# Delayed workflow run logs

- Provider: [Knock](https://down.guide/providers/knock)
- Confidence: Confirmed
- Impact: Degraded
- lasted 29m
- started 2026-02-10 00:50 UTC
- id: DWN-079c2cf12d
- Official page: https://status.knock.app/incidents/01KH2GEYRSDDBTNR9NX5XCF4CP

## Updates from Knock
### 2026-02-10 00:50 UTC: investigating
We're currently investigating an issue with delayed workflow run logs. Workflow execution and message delivery are unaffected, but our log queues are currently behind.

### 2026-02-10 01:07 UTC: identified
We’ve shipped a fix to improve throughput for our consumer that processes workflow run logs and are beginning to see the consumer catch up on its backlog. We’re continuing to monitor closely.

### 2026-02-10 01:12 UTC: monitoring
Workflow run logs are no longer delayed. We are monitoring closely before closing this out.

### 2026-02-10 01:20 UTC: resolved
This incident has now been resolved and the service is now fully operational.

From the builder: does your app depend on Knock? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=knock) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Knock.

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