Retrospective incident report — October 13, 2026. This incident is resolved. This entry was added after recovery; its publication timestamp is not the outage start time.

Impact
Users experienced errors and timeouts when loading Contacts, Campaigns, Problems and Signals in the Outcomet app. The total number of affected accounts and requests, and the exact outage duration, were not measured.

Cause
A frontend release was published before four required corrective database migrations had reached production. The resulting mismatch left obsolete database access policies and query paths active, causing read requests to fail or time out.

Recovery
The corrective migrations were applied successfully. The obsolete policies were removed, sampled authenticated reads succeeded, and the inspected post-recovery database logs contained no statement timeouts. No evidence of data loss was identified during the response.

Timeline (UTC, October 13)
• 13:49:52 — Frontend release published.
• 13:55:25 — Corrective database migrations completed.
• From 13:56 — Recovery checks confirmed successful sampled reads and no statement timeouts in the inspected log window.
• 19:01:26 — The first release using the new deployment gate was published successfully, after its database check completed and the same commit was promoted.

The approximately 5 minutes 33 seconds between frontend publication and migration completion is the confirmed release mismatch interval, not a measurement of the full outage duration.

Prevention and verification
Production frontend publication now depends on successful CI, successful database migrations and deployment of any changed Edge Functions. Only then is the same commit promoted for frontend publication. Failed checks block promotion. The first automatic release through this gate was verified successfully in production; the deployment-gate remediation is complete.

We are sorry for the disruption. Quantifying the full historical impact remains a follow-up.