beenherebefore e0c0167428 fix(cron): use last_run_at as croniter base for cron jobs ... compute_next_run() ignored the last_run_at parameter for cron-type schedules, always computing from _hermes_now() instead. This was inconsistent with interval jobs which DO use last_run_at as the anchor. After a crash or restart, cron jobs would compute next_run_at from the arbitrary restart time rather than the actual last execution time. While the stale detection in get_due_jobs() catches most cases, using last_run_at as the croniter base eliminates edge cases and makes the behavior consistent across schedule types. Salvaged from #9014 (authored by @beenherebefore) onto current main. The original PR branch was 2+ weeks stale and would have reverted substantial unrelated work (jobs_file_lock, workdir/context_from/ enabled_toolsets, issue #16265 state=error recovery). Kept just the 7-line substantive fix and the regression test.		2026-04-29 08:24:48 -07:00
..
__init__.py	docs: clarify gateway service scopes (#1378)	2026-03-14 21:17:41 -07:00
jobs.py	fix(cron): use last_run_at as croniter base for cron jobs	2026-04-29 08:24:48 -07:00
scheduler.py	fix(cron): fall back gracefully when HERMES_CRON_TIMEOUT is invalid	2026-04-29 08:21:04 -07:00