Re-checked every 30s. Postgres is required; a queue outage degrades background grading only.

Where a failure goes, and what runs on its own. An unrouted alert or an unregistered sweep makes everything above look healthier than it is.

The failures that don't throw — a half-graded event, an autosave that never landed, data moving under issued results. Not run automatically: the scans take seconds and a breach raises an alert.

Grouped by action + message. Includes browser crashes (client.error) alongside rejected server calls — during an incident the count and the shape matter more than the distinction.