feat(cron): warn when gateway not running on cron create/list - #51696
Merged
Conversation
The cron ticker only runs inside the gateway (_start_cron_ticker); there is no standalone cron daemon. When the gateway isn't running, next_run_at passes but jobs never fire and last_run_at stays null — and manual 'hermes cron run' (which bypasses the ticker) appears to work, masking the real cause. This is the most common cron support report (#51038). cron list already warned; extend the same warning to cron create (the moment the user is most likely to hit this) via a shared helper, and add a pointer to 'hermes cron status'. Silent when a gateway is running, so the gateway /cron path is unaffected.
Contributor
🔎 Lint report:
|
alt-glitch
added
type/feature
pai-scaffolde
pushed a commit
to pai-scaffolde/hermes-agent
that referenced
this pull request
Jun 28, 2026
…search#51696) The cron ticker only runs inside the gateway (_start_cron_ticker); there is no standalone cron daemon. When the gateway isn't running, next_run_at passes but jobs never fire and last_run_at stays null — and manual 'hermes cron run' (which bypasses the ticker) appears to work, masking the real cause. This is the most common cron support report (NousResearch#51038). cron list already warned; extend the same warning to cron create (the moment the user is most likely to hit this) via a shared helper, and add a pointer to 'hermes cron status'. Silent when a gateway is running, so the gateway /cron path is unaffected.
1 task
waefrebeorn
pushed a commit
to waefrebeorn/slermes
that referenced
this pull request
Jul 2, 2026
…search#51696) The cron ticker only runs inside the gateway (_start_cron_ticker); there is no standalone cron daemon. When the gateway isn't running, next_run_at passes but jobs never fire and last_run_at stays null — and manual 'hermes cron run' (which bypasses the ticker) appears to work, masking the real cause. This is the most common cron support report (NousResearch#51038). cron list already warned; extend the same warning to cron create (the moment the user is most likely to hit this) via a shared helper, and add a pointer to 'hermes cron status'. Silent when a gateway is running, so the gateway /cron path is unaffected.
habarmc1223-sudo
pushed a commit
to habarmc1223-sudo/hermes-agent-fluxmem
that referenced
this pull request
Jul 8, 2026
…search#51696) The cron ticker only runs inside the gateway (_start_cron_ticker); there is no standalone cron daemon. When the gateway isn't running, next_run_at passes but jobs never fire and last_run_at stays null — and manual 'hermes cron run' (which bypasses the ticker) appears to work, masking the real cause. This is the most common cron support report (NousResearch#51038). cron list already warned; extend the same warning to cron create (the moment the user is most likely to hit this) via a shared helper, and add a pointer to 'hermes cron status'. Silent when a gateway is running, so the gateway /cron path is unaffected.
santhreal
pushed a commit
to santhreal/hermes-agent
that referenced
this pull request
Jul 13, 2026
…search#51696) The cron ticker only runs inside the gateway (_start_cron_ticker); there is no standalone cron daemon. When the gateway isn't running, next_run_at passes but jobs never fire and last_run_at stays null — and manual 'hermes cron run' (which bypasses the ticker) appears to work, masking the real cause. This is the most common cron support report (NousResearch#51038). cron list already warned; extend the same warning to cron create (the moment the user is most likely to hit this) via a shared helper, and add a pointer to 'hermes cron status'. Silent when a gateway is running, so the gateway /cron path is unaffected.
Gravezzz
pushed a commit
to Gravezzz/hermes-agent
that referenced
this pull request
Jul 21, 2026
…search#51696) The cron ticker only runs inside the gateway (_start_cron_ticker); there is no standalone cron daemon. When the gateway isn't running, next_run_at passes but jobs never fire and last_run_at stays null — and manual 'hermes cron run' (which bypasses the ticker) appears to work, masking the real cause. This is the most common cron support report (NousResearch#51038). cron list already warned; extend the same warning to cron create (the moment the user is most likely to hit this) via a shared helper, and add a pointer to 'hermes cron status'. Silent when a gateway is running, so the gateway /cron path is unaffected.
This was referenced Jul 29, 2026
leewenjie
pushed a commit
to leewenjie/hermes-agent
that referenced
this pull request
Aug 7, 2026
…search#51696) The cron ticker only runs inside the gateway (_start_cron_ticker); there is no standalone cron daemon. When the gateway isn't running, next_run_at passes but jobs never fire and last_run_at stays null — and manual 'hermes cron run' (which bypasses the ticker) appears to work, masking the real cause. This is the most common cron support report (NousResearch#51038). cron list already warned; extend the same warning to cron create (the moment the user is most likely to hit this) via a shared helper, and add a pointer to 'hermes cron status'. Silent when a gateway is running, so the gateway /cron path is unaffected.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
hermes cron createnow warns when the gateway isn't running, so users learn up front that their job won't fire.The cron ticker runs only inside the gateway (
_start_cron_ticker) — there is no standalone cron daemon. With no gateway running,next_run_atpasses but jobs never fire andlast_run_atstays null. Manualhermes cron runbypasses the ticker and appears to work, masking the cause. This is the most common cron "jobs never fired" report (#51038).cron listalready showed this warning;cron create(the moment the user is most likely to hit it) did not.Changes
hermes_cli/cron.py: extract the warning into_warn_if_gateway_not_running(); call it fromcron_createandcron_list(dedup); add ahermes cron statuspointer. Silent when a gateway is running — the gateway/cronpath is unaffected.tests/hermes_cli/test_cron.py: regression guards — create/list warn when gateway absent, silent when present.Validation
cron createcron listVerified live: real
find_gateway_pids()returned a running PID → no false nag; forced-absent → warning renders. Targeted suite 7/7 green viascripts/run_tests.sh.Note on #51038
The reported scheduler defect (polling too slow / no catch-up) does not exist: the ticker polls every 60s and daily jobs already get a 2h catch-up grace window (verified E2E — a daily job 13–23 min late fires; >2h fast-forwards). The real cause was a gateway that was never started. This PR closes the UX gap that led to the report.
Infographic