mirror of
https://github.com/prosolis/gogobee.git
synced 2026-07-15 08:32:41 +00:00
ecca66da58
Locks were gated behind the same once-per-day 08:00 UTC tick as floor resolution. A run created after morningHour would wait until next day's tick to be eligible — meaning actual lock latency could be 24-48h, not the 24h advertised. Worse, a run created late on Day N missed the Day N+1 tick (too early) AND the Day N+2 tick happens 48h after creation. Fix: lock checks fire on every ticker minute (cheap timestamp scan over typically 0-5 open runs). Resolution stays daily, gated by JobCompleted. Real symptom that prompted this: Run #1 created 17:17 UTC, locked never fired because the morning tick at 08:00 UTC the next day saw the run as not-yet-eligible (only 15h elapsed), then marked the daily job complete before the actual 24h elapsed at 17:17 UTC. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>