Trigger.dev experienced a minor incident on January 23, 2026 affecting Current status by service (Trigger.dev cloud), lasting 2h 42m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 23, 2026, 01:37 AM UTC
We are experiencing intermittent issues that may cause some task runs to fail. Automatic retries are in place and should recover most affected runs. Our team is actively working on resolution.
- resolved Jan 23, 2026, 04:19 AM UTC
Full service has been restored. Task execution is back to normal. If you experienced failures between 01:37 and 04:19 UTC, those runs can be retried successfully now. What happened: During a period of high activity, a backlog of completed runs built up faster than our cleanup processes could handle, which put pressure on internal services and caused intermittent failures. What we did: We spun up additional cleanup capacity to clear the backlog and restore normal operation. What we're doing next: We're increasing resource limits on critical internal services and adding better alerting so we can catch this earlier if it happens again.