# Run logs are being dropped

- Provider: [Trigger.dev](https://down.guide/providers/trigger-dev)
- Confidence: Confirmed
- Impact: Degraded
- lasted 30m
- started 2026-09-28 07:20 UTC
- OpenTelemetry
- id: DWN-add8f17d68
- Official page: https://status.trigger.dev/incidents/1076016

## Updates from Trigger.dev
### 2026-09-28 07:20 UTC: degraded
We're investigating run logs being dropped (from your run when you do console.log/logger.log). This doesn't impact run operation but does impact observability.
This isn't due to a code or configuration change. More information soon.

### 2026-09-28 07:50 UTC: resolved
Logs are being fully ingested again. 
The issue was with the internal workers in our shared OpenTelemetry service. They became unhealthy but weren't rolled. We're looking into why and how to prevent this from happening again.

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