[Bug] Scheduled agent runs delayed 20-150+ minutes past cron trigger time

Bug Description
--- Title: Scheduled agent runs starting 30–40+ min after cron time Summary: My scheduled trigger field-guardian (id trig_018G3wzNgKrDLfxYjmzeTe5o, cron 0 14 *) has been starting well after the scheduled UTC minute. Evidence: - 2026-04-22: scheduled 14:00 UTC, UI shows run start at 14:38 UTC (38 min slip). Commit landed at 14:42 UTC, so agent execution itself was only ~4 min — the entire delay is pre-run queue time. - 2026-04-20: agent commits at 16:24 and 16:30 UTC for a 14:00 UTC cron (>2 hr slip). - 2026-04-21: commit at 14:22 UTC (~22 min slip). - next_run_at in the trigger API reports 14:02:57Z — so the API advertises ~3 min of jitter, but actual dispatch is much later. Expected: Runs dispatch within a minute or two of the cron time. Actual: 20–150 min slip on consecutive days. Impact: Daily reports to end-users arrive unpredictably late. Time-sensitive actions (e.g. weather-dependent recommendations) lose relevance. Suspect: Contention on :00 cron minute — many users schedule at the top of the hour. Trigger management URL: https://claude.ai/code/scheduled/trig_018G3wzNgKrDLfxYjmzeTe5o

Environment Info

• Platform: darwin
• Terminal: Apple_Terminal
• Version: 2.1.117
• Feedback ID: 36632597-9288-42c7-b00c-ea535fa6b989

Errors

[]