Skip to main content
Trigger.dev

Batches are slow to process

Degraded Lasted 5h 10m · started · Trigger.dev's page

Level
confirmed
Worst impact
Degraded
Down Index
21of 100

What to do

  • Check whether your product depends on Trigger.dev. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 5h 10m it lasted.

    Anything that failed between 2026-01-01 10:00 UTC and 2026-01-01 15:10 UTC may need a replay.
  • Subscribe to Trigger.dev's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=trigger-dev works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Trigger.dev 3

  1. update

    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

    provider

  2. update

    The batches are now processing much faster. The issue was the default batch processing concurrency for an organization was too low. Organizations that were already on Hobby or Pro had higher concurrency but newer orgs didn't. This created a backlog. We've increased the default processing concurrency for each org and will look at the upgrade path for paid customers as well. We're monitoring the processing – it should get back to near realtime soon.

    provider

  3. resolved

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

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-5e4172a1a0

Is Trigger.dev still down?

No, this incident was resolved 2026-01-01 15:10 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.

How long did it last?

5h 10m, from 2026-01-01 10:00 UTC to 2026-01-01 15:10 UTC, by the times Trigger.dev posted.

What caused it?

Trigger.dev hasn't published a root cause. If it does, it shows here.

Where does this come from?

Trigger.dev's official status page, https://status.trigger.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.