# Issue with task logs

- Provider: [Trigger.dev](https://down.guide/providers/trigger-dev)
- Confidence: Confirmed
- Impact: Degraded
- lasted 41m
- started 2026-01-16 17:03 UTC
- id: DWN-73aa48301a
- Official page: https://status.trigger.dev/incident/805855

## Updates from Trigger.dev
### 2026-01-16 17:03 UTC: update
Our task log storage system is currently overloaded and we are working on bringing up additional capacity, but in the meantime some logs may be lost.

### 2026-01-16 17:44 UTC: resolved
We have finally been able to provision additional capacity and logs are working again. A full post-mortem will follow.

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-73aa48301a), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.