# Dashboard runs list is delayed

- Provider: [Trigger.dev](https://down.guide/providers/trigger-dev)
- Confidence: Confirmed
- Impact: Degraded
- lasted 1h 44m
- started 2026-01-21 15:48 UTC
- id: DWN-9b050ca538
- Official page: https://status.trigger.dev/incident/809042

## Updates from Trigger.dev
### 2026-01-21 15:48 UTC: update
Our run sync to clickhouse process is currently delayed. The runs list in the dashboard will be behind but runs are executing as normal.

### 2026-01-21 16:49 UTC: update
The dashboard runs list is now live again but some v3 logs are being dropped because of ingestion problems. We're investigating and will provide an update as soon as we have anything

### 2026-01-21 17:32 UTC: resolved
The root cause of the issue was a failed upgrade of our clickhouse service from 25.6 to 25.8. While the service failed to rollout, the rollback also failed and so our clickhouse service was split between some instances on 25.6 and 25.8, which caused various issues. Our clickhouse provider is continuing to investigate the failed release but we can confirm that the rollback has completed and queries are back to normal.

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