# Delayed processing of workflow logs

- Provider: [Knock](https://down.guide/knock)
- Level: confirmed
- Impact: Degraded
- lasted 1h 56m
- started 2026-06-15 14:35 UTC
- id: DWN-321ed19d0f
- Official page: https://status.knock.app/incidents/01KV5VAZ6FZJ0NBTQGB38HV61N

## Updates from Knock
### 2026-06-15 14:35 UTC: monitoring
We intermittently experienced delayed workflow logs between ~09:00 AM UTC and ~01:45 PM UTC today (2026/06/15). This was caused by some internal changes in how we fan out workflow logs, which caused consumers to get temporarily backlogged. The peak delay we experienced before processing workflow logs was around 15 minutes, but we intermittently saw delays of up to 5-6 minutes.
This affected
1. Logs showing up in the dashboard.
2. Workflow batch mappings.
We saw complete resolution at 01:43 PM UTC. Logs are being processed within our usual window (within up to ~5s) again.

### 2026-06-15 16:31 UTC: resolved
We did not experience any further issues after we put the fix in place.

---
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://sazabi.com/?utm_source=down-guide&utm_medium=markdown).