Trigger.dev experienced a minor incident on December 4, 2025 affecting Current status by service (Trigger.dev cloud), lasting 19m. The incident has been resolved; the full update timeline is below.
Affected components
Current status by service (Trigger.dev cloud)
Update timeline
- investigating Dec 04, 2025, 03:16 PM UTC
The runs list is currently showing stale data. Runs are executing like normal. Our replication process from postgresql to our Clickhouse instance is falling behind and so the dashboard will be showing stale run data. We're investigating.
- investigating Dec 04, 2025, 03:35 PM UTC
The runs list has all caught up and the dashboard is no longer displaying stale data. We're continuing to investigate the root cause of this issue