# Batches are slow to process

- Provider: [Trigger.dev](https://down.guide/providers/trigger-dev)
- Confidence: Confirmed
- Impact: Degraded
- lasted 5h 10m
- started 2026-01-01 10:00 UTC
- id: DWN-5e4172a1a0
- Official page: https://status.trigger.dev/incident/797058

## Updates from Trigger.dev
### 2026-01-01 10:00 UTC: 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

### 2026-01-01 14:33 UTC: 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.

### 2026-01-01 15:10 UTC: resolved
The new batch concurrency processing defaults have brought the processing queue down to zero

From the builder: does your app depend on Trigger.dev? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=trigger-dev) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Trigger.dev.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-5e4172a1a0), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.