Account Health

Account health answers one question: is anything wrong with my account right now?

• Live faults only — a feed that stopped fetching, an import that failed, a store of yours that stopped answering.
• Not whether your search is set up well — that is something else.
• Worked out fresh on every page load. Nothing is stored.

The dot on your account picture

• Red — your data is out of date or broken now.
• Amber — worth knowing about; your data is still flowing.
• No dot — nothing is wrong. No green tick, no counter sitting at zero.
• The account menu always carries Account health, dot or no dot, with the number of issues.

The Account health page

• One row per issue, worst first: severity, what happened in plain words, when it started, and a link to the thing itself — Error — The “tmdb-films” feed is not updating — since 5 August.
• All clear reads Nothing needs attention. A check that could not run says so instead.
• Separate from Profile (name, email, country, password, account picture).
• Rows only cover things you still have — delete a list and its rows go too.

Snoozing a row

Each row carries Snooze for a week, for something you already know about.

• Back after seven days if the problem is still there.
• Back sooner if it gets worse — snoozing a warning does not silence the error it turns into.
• The panel says how many rows are snoozed, even when nothing else is wrong.
• Account-wide, not personal: it quietens the panel for your colleagues too.
• Needs permission to edit the account; reading the panel is not enough.
• Deleting a list clears its snoozes, so a new list of the same name starts with nothing hidden.

What is checked

Check	Raises	What it means
A feed has stopped updating	Error	The source refused us or could not be reached; the row carries its reason. Lists fed by it are quietly out of date.
An import failed	Error	The latest import into a list stopped on your file or store — a bad row, a file too big, a store out of reach.
An import was interrupted	Warning	We stopped the run, not you — a release, a restart. It retries; nothing for you to fix.
A connected service is not responding	Error	One of your media stores, search services, caches, telemetry destinations or judges has failed several checks in a row.
A gate backfill did not finish	Error	A gate changed, and the job re-applying it to existing records stopped part way, so some records hold their old values.
Automatic syncing is paused	Warning	Your plan pauses background syncing after a stretch with no sign-in. Signing in resumes it.

One or two failures raise nothing.

“Switched off” is the one to read carefully

A service that fails long enough is dropped: we stop trying it and stop syncing against it. The row then says switched off rather than not responding.

• Fixing your end is not enough — we no longer check it, so nothing here notices it come back.
• Repair it, then resume it from its own page: fix your media store, then open the store’s page and resume.
• Nothing has been deleted meanwhile.

“We could not check everything”

A check that cannot read what it needs says so, rather than reporting all clear. Nothing is wrong and we could not look are different answers.

Ask the assistant

• Ask the assistant on a row opens the assistant with that issue described. It reads the error, looks at the setup, and often fixes it — for example, why a source refused your feed.
• The checks are free and always run; an assistant turn costs one credit, spent only on the issue you choose.
• Nothing greets you at sign-in to say something is wrong.

When we email you

• A feed failing to fetch three times in a row emails the account owner once — not once per failure.
• The next successful sync resets it, so a later problem gets a fresh email.

Over the API

The same answer, for a script or a status page of your own:

GET /account/issues/{account-name}

Field	What it holds
severity	error or warning.
since	When it started, or null where there is no such moment — a paused sync began at no particular instant.
target.kind	Inside each issue’s target: feed, list, account, media-store, search-service, cache-service, model or telemetry-sink.
target.name	A name, not a link, so it passes straight to another call — tmdb-films is what you give the feed API.
checks_run / checks_total	An empty issues array means a healthy account only when the two match. A lower checks_run means the answer is incomplete.
dismissed	How many real issues are snoozed and so missing from issues. Above zero is not a healthy account.

Snoozing is console-only and has no API. Full shape in the API reference under Account. Both clients carry it:

var health = await client.Account.GetHealthAsync("acme");

const health = await client.account.getHealth("acme");

For agents

MCP: account_health — read-only, costs nothing, and the right first call when a search returns out-of-date results. It separates “the data really is old” from “the query is wrong” in one step.

Notes

• Nothing is stored, so a problem that fixes itself disappears — nothing to mark as read, no history.
• The exception is a snooze, which lapses after a week.
• Faults on our side never appear here.
• Anyone who can read the account sees the same panel, contributors included.
• Webhook deliveries are not covered yet.
• Not Recommendations in Insights: that is standing advice about your setup, this is a live fault that clears when the thing recovers.