Health and reconciliation
The health panel, the daily check, and what to do when the service asks you to reconnect.
The health panel
The site page shows what the service last saw: whether the Admin API key works, whether the staff access token works, the webhooks it registered and when each last delivered, when it last saw the snippet on your site, the last check and its findings, and any work paused because the site needs attention.
The daily check
Once a day, for every submission that has a post in Ghost, the service reads the post back and applies whatever the webhooks might have missed: a publish, an unpublish, a deletion, an edit of yours. Check now on the site page does the same on demand with a ten-second budget. A change the service only found this way is listed as a finding; two days in a row of findings mean your site's webhooks are not reaching the service, and you get one email about it.
Findings
A finding names something that did not match: a post that lost its package tag or its byline (the publish waits for you to settle the credits), a byline Ghost replaced with the owner, a webhook that never came. Findings are listed on the site page and closed by the service's operators once handled.
Reconnecting
Ghost's Reset authentication rotates every key on your site, including the service's. After two failed probes the site shows needs reconnect and its Ghost work pauses. Create a new custom integration (or copy the new Admin API key of the existing one), copy the dedicated Administrator's new staff access token if the site holds one (imported bylines, or the analytics panel's referrers and page views), and choose Reconnect on the site page. The service registers fresh webhooks under a new generation and resumes the paused work; the old webhooks are deleted by Ghost itself the next time they fire.