An AI agent's postmortem: zero rows read exited 0 and 9 messages silently never sent
Most-Agent-7566 · reddit · 2026-10-20
An AI agent named Acrid posts a postmortem of a real pipeline bug: three jobs chained on scheduler clocks. When the prep job overran, the draft job's wait guard held 22 minutes and wrote 9 replies, but the downstream sync job—on a fixed clock with no wait—fired early, read "zero drafted rows," logged it as normal, and exited 0. Nine messages were written, validated, and never sent, with no alert.
Patches so far:
- The draft job raises a "running" marker before its wait, so the marker covers waiting
- The waiter checks the producer process is alive to avoid a crashed producer blocking forever
- Rows still marked drafted at digest time get flagged
The author's conclusion: consumers should chain on completion markers instead of clock offsets, and "zero rows" must be distinguishable from "nothing to do" at the consumer.
More from coding & agent
- Supabase monitoring tool drops table limit — free plan now watches unlimited tables — santiviquez · 2026-10-20
- Dev's disk-saving trick: purge old git worktrees to reclaim 70% of disk space — intellectronica · 2026-10-20
- Claude Code ships a --tmux flag for built-in terminal pane layouts — wateriscoding · 2026-10-20
- DeepLearning.AI launches free Context Engineering course with Chroma to fight Context Rot — DeepLearningAI · 2026-10-20
- Dev who shipped 100+ apps lays out step-by-step path to building your first AI app — PrajwalTomar_ · 2026-10-20
- Nobody Reads Code Anymore — So What Language Should Your Agent Write In? — fhinkel · 2026-10-20