Operator diagnostics
Inspect redacted platform-wide publishing health with an explicit operator allowlist.
EveryFeed includes a platform health workspace for trusted self-hosted operators. It summarizes published root posts, new channel connections (any that aren't disabled), failed post or thread items, and provider-level distribution for a selected date range, plus an all-time organizations total. The same Operator area also hosts support and announcement tooling beyond the diagnostics covered here.
Grant access
Add the exact user UUIDs to the API environment as a comma-separated allowlist:
OPERATOR_USER_IDS=USER_UUID_ONE,USER_UUID_TWOThe user UUID is the user.id field returned by GET /auth/me. Restart the
API after changing the environment. Authorized users then see Operator in
the workspace sidebar. Organization admin status alone does not grant operator
access.
Keep the allowlist narrow
Operator diagnostics aggregate signals across every organization. Use stable user UUIDs, remove former operators promptly, and never expose this route through a shared account.
Inspect failures safely
The failure table can be filtered by date and provider, with unknown errors prioritized. Each row contains only the organization and connection identity, post ID, timestamps, and two bounded, redacted strings: the error message and the provider's error body.
EveryFeed deliberately omits post copy, media, access tokens, and user email addresses. Common bearer credentials, OAuth query values, API keys, cookies, passwords, and secrets are masked at capture time, before the diagnostic is ever stored — what you see is all that exists.
Choose Inspect to view the safe diagnostic or copy it for an internal issue. The API limits a single range to 366 days and a page to 100 records.