Skip to main content
Settings → Admin → Health, or ask:
Is anything broken on this instance?

What health checks

admin_health is the first tool to call when something is reported broken, and the one to call on a schedule if you check on the instance at all. Each check comes back ok, warn or down with a plain-language summary you can read out as-is. Two readings worth knowing:
  • Billing down usually means the signing secret in Admin → Configuration → Billing is wrong.
  • Billing “never called” means the webhook endpoint was never added on Stripe’s side.

What failed

admin_recent_errors is the instance’s own event stream, newest first: failed emails, Stripe webhooks that did not verify or did not sync, tool calls that threw, and pages that errored. Each entry has a level — INFO, WARN or ERROR — a source, a one-line message, and the address of whoever’s request hit it.
Pass level: "ERROR" for failures only. The default includes INFO entries such as successful webhook deliveries — those are what prove Stripe is still reaching this instance at all, so the noisy default is the useful one when you are debugging billing.
Entries older than 30 days are removed automatically. Default 50 entries, maximum 200.
This never contains anyone’s content. When a tool call throws, the tool’s name and the failure are recorded — the arguments that caused it deliberately are not, because those are somebody’s career history and every admin can read this stream.

Two questions this answers well

Did that invite to priya@example.com actually send?
admin_user_detail says whether it left; admin_recent_errors with source: "email.send" says why it did not.
Is anyone actually using their assistant?
The health check reports when a tool call last arrived. list_connections on an individual account shows the same thing per client, including what called in.