Trigger.dev incident

Batches are slow to process

Major Resolved View vendor source →

Trigger.dev experienced a major incident on January 1, 2026 affecting Current status by service (Trigger.dev API), lasting 5h 10m. The incident has been resolved; the full update timeline is below.

Started
Jan 01, 2026, 10:00 AM UTC
Resolved
Jan 01, 2026, 03:10 PM UTC
Duration
5h 10m
Detected by Pingoru
Jan 01, 2026, 10:00 AM UTC

Affected components

Current status by service (Trigger.dev API)

Update timeline

  1. investigating Jan 01, 2026, 10:00 AM UTC

    There is a backlog in processing batchTrigger and batchTriggerAndWait calls. This means runs are being created slower than normal for these. We're investigating why this is happening

  2. resolved Jan 01, 2026, 03:10 PM UTC

    The new batch concurrency processing defaults have brought the processing queue down to zero