Error Alerting API Polls — Unresolved Groups Across Cohort Experiments

<p>Short answer: choose a cheap metrics dashboard API for a SaaS app only after it preserves experiment exposure, cohort, and rollback-window semantics under a strict

<p>Short answer: use separate signals for an exception, a missed schedule, an unfinished run, and an invalid result. Exception capture is necessary for cron jobs, workers, and web

<p>Keep one searchable record per failure group, a bounded sample of its events, and immutable state transitions for resolution and rollback. That is the least complex admin page

<p>Short answer: for a small SaaS notification service, the best inexpensive logging choice is the one that preserves enough evidence to reconstruct a failed delivery without