# Trigger.dev: Runs list/logs degraded

- Provider: [Trigger.dev](https://outages.live/triggerdev.md)
- Type: Incident
- State: Resolved
- Worst impact: Degraded performance
- Started: 2026-09-03 14:56 UTC
- Resolved: 2026-09-03 16:20 UTC (lasted 1 h 24 min)
- Components: Dashboard, API, OpenTelemetry
- Official update: https://status.trigger.dev

## Updates from Trigger.dev

### resolved, 2026-09-04 12:55 UTC

# Postmortem: Missing task logs and traces Date: 2026-09-03 Duration: ~67 minutes Impact: New logs, spans and trace data for some runs were not stored and cannot be recovered ## Summary Between approximately 14:35 and 15:43 UTC on 2026-09-03, batches of new task events (the logs, spans and span events that make up a run's trace) were rejected by ClickHouse, the database behind the trace view, logs view and event search. Each batch was retried three times over about 1.5 seconds and then dropped. The events in those batches are permanently lost. Run execution, run status and the runs list were unaffected throughout, as were logs and traces that had already been stored. We are sorry for the missing data and for making affected runs harder to understand. ## What customers experienced Runs that were emitting logs or spans during the window may have a trace that is empty or missing spans, depending on which of their batches happened to land. The dashboard did not return errors: reads succeed

### resolved, 2026-09-03 16:20 UTC

The ingestion delay is down to normal levels. A post-mortem will follow.

### degraded, 2026-09-03 15:50 UTC

Run logs/traces are inserting and the ingestion delays for are coming down. We have fixed the underlying issue. We will resolve this issue with more details when the ingestion delays are back to normal.

### degraded, 2026-09-03 15:28 UTC

We have identified the root cause of the issue and are working towards mitigating the issue. Currently the run list dashboard and API are fine, but we aren't able to insert new run logs and trace data.

### degraded, 2026-09-03 14:56 UTC

The insert delay for the runs list and logs is longer than usual. This impacts the dashboard and APIs associated with listing runs and viewing run logs. This is being caused by higher load and slow auto-scaling in our ClickHouse cluster.