# Runs list is lagging behind

- Provider: [Trigger.dev](https://down.guide/providers/trigger-dev)
- Confidence: Confirmed
- Impact: Degraded
- lasted 19m
- started 2025-12-04 15:16 UTC
- id: DWN-d7be025662
- Official page: https://status.trigger.dev/incident/779688

## Updates from Trigger.dev
### 2025-12-04 15:16 UTC: update
The runs list is currently showing stale data. Runs are executing like normal. Our replication process from postgresql to our Clickhouse instance is falling behind and so the dashboard will be showing stale run data. We're investigating.

### 2025-12-04 15:31 UTC: update
We are slowly catching up with live run data and should be back to normal operation very soon.

### 2025-12-04 15:35 UTC: resolved
The runs list has all caught up and the dashboard is no longer displaying stale data. We're continuing to investigate the root cause of this issue

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