teknium1 4768ea624d fix: skip stale cron jobs on gateway restart instead of firing immediately ... When the gateway restarts after being down past a scheduled run time, recurring jobs (cron/interval) were firing immediately because their next_run_at was in the past. Now jobs more than 2 minutes late are fast-forwarded to the next future occurrence instead. - get_due_jobs() checks staleness for cron/interval jobs - Stale jobs get next_run_at recomputed and saved - Jobs within 2 minutes of their schedule still fire normally - One-shot (once) jobs are unaffected — they fire if missed Fixes the 'cron jobs run on every gateway restart' issue.		2026-03-16 23:48:14 -07:00
..
__init__.py	test: add unit tests for 8 modules (batch 2)	2026-02-26 13:54:20 +03:00
test_jobs.py	fix: skip stale cron jobs on gateway restart instead of firing immediately	2026-03-16 23:48:14 -07:00
test_scheduler.py	fix(cron): support per-job runtime overrides	2026-03-14 22:22:31 -07:00