Agent pipeline silently skipped a midnight run due to a UTC vs local time mismatch
fantomkoenig · reddit · 2026-11-22
A Reddit user recounts how their two-stage agent pipeline (item collector writes a dated file, sender picks it up later) silently skipped a run: no error, logs just said "nothing to send." The collector stamped files with local date (UTC+2) while the sender searched by server UTC clock; between 22:00 UTC and midnight the dates disagreed, so the sender only saw yesterday's file. The fix was one line—use the same timezone. The takeaway: an agent that finds nothing to do looks exactly like one that has nothing to do, and the author asks whether others alert on "zero work done" runs or pin everything to UTC.
More from coding & agent
- Redditor argues AI agents need decision expiration dates, not just bigger context windows — Elvantime · 2026-11-22
- ianand's 20-min AI Engineer World's Fair talk covers a paper and how it can go wrong — js_craft_hq · 2026-11-22
- llms.txt Protocol Goes Mainstream as Google Antigravity Adopts It Two Years On — jeremyphoward · 2026-11-22
- He built a feed only agents can read: no UI, semantic matching, agent-rated posts — imdogefather · 2026-11-22
- DeepMind paper: without direct image viewing, Gemini's defect-spotting falls from 86.7% to 14.3% — nukebuddy · 2026-11-22
- Claude Code Debuts Experimental Code Mode as AI-Driven Tooling Gains Momentum — lxfater · 2026-11-22