How do I stop a running Hermes job without deleting its schedule?
Use cancel to request that the current Hermes scheduled run stop while keeping its schedule. Use pause as well if you want to prevent future scheduled runs while you investigate. Cancel is a request: check that the run has been recorded as cancelled before treating it as stopped.
This follows Hermes Agent v0.23.1, commit 3b42157, checked on 15 November 2026. We reviewed official documentation and source; we have not tested a live cancellation or measured how quickly it stops on a Vavio computer. The commands below are upstream Hermes commands, not Vavio CLI commands.
Which control do I need?
| What you want | Control | Effect on the schedule |
|---|---|---|
| Stop this run and let the recurring job continue later | Cancel | Keeps the job and its enabled or paused state. |
| Stop future scheduled runs while leaving the current run alone | Pause | Keeps the job, disables scheduled fires. |
| Stop this run and hold future scheduled runs for review | Pause, then cancel | Keeps the job paused until you resume it. |
| Delete the job entirely | Remove | Deletes the job and requests cancellation of an external live run. |
Pausing does not interrupt a run already executing. Removing has a larger effect than cancelling: it also deletes that job’s saved output folder and notepad. Keep the job if you need its configuration or output to investigate.
How do I ask Hermes to stop just this run?
Ask in chat, naming the job and the scope of the stop. For example:
List my scheduled jobs. Cancel the current run of “Morning research” because it is stuck waiting on the source website. Keep its schedule. Then show me the recorded run outcome and its next scheduled time.
Hermes’s cron management tool supports a cancel action. If more than one job has the same name, use the ID from the job list. The pinned version refuses ambiguous names rather than choosing one.
If you have access to the Hermes command line, the equivalent is:
hermes cron list
hermes cron cancel <job_id> --reason "Stuck waiting on the source website"
hermes cron runs <job_id> --limit 20
Replace <job_id> with the actual ID. The cancel command prints Cancel requested, including the execution ID. That acknowledgment means the request was recorded; it does not mean the run has already finished stopping.
Upstream’s cron guide also documents a Stop control in its Desktop job view, changing to Stopping… while cancellation is pending. This is upstream UI documentation, not proof of that control in Vavio’s installed Hermes interface. Chat or the supported Hermes command line gives the underlying operation explicitly.
What happens after I request cancellation?
The request targets one execution of the job. A leftover request cannot cancel its next scheduled execution.
For a script run, the documented teardown terminates the script’s process group, starting with SIGTERM and escalating to SIGKILL after a grace period. For an agent run, Hermes interrupts the turn at a cancellation checkpoint. Neither path promises an instantaneous stop, and this review does not establish a maximum wait.
When the run books its cancellation, its history records cancelled with the reason. Hermes does not send a failure notice for that cancellation or increase the job’s failure streak. The source still advances normal run bookkeeping: a cancelled scheduled occurrence normally counts toward a finite repeat limit. Manual extra runs and retry attempts for an already-counted occurrence are exceptions. A job limited to a fixed number of runs may therefore finish its allowance when you cancel a scheduled occurrence. Check its remaining repeats as well as its next time.
If nothing is running, cancel reports that there is nothing to cancel. If the run has already completed, a later request cannot turn that completed outcome into a cancellation.
What if I need time to fix the job?
Pause it first, then cancel its current execution:
hermes cron pause <job_id>
hermes cron cancel <job_id> --reason "Paused for investigation"
hermes cron runs <job_id> --limit 20
hermes cron list --all
Check both facts: the intended execution has stopped, and the job remains paused. Pausing prevents scheduled fires. Ordinary chat or CLI attempts to run a paused job can be refused; a forced trigger can resume the job as part of running it. Recheck its scheduling state after any test rather than assuming it stayed paused.
After the fix, hermes cron resume <job_id> re-enables scheduling. For a recurring job whose due time passed while paused, the default policy can produce one catch-up run. Setting cron.catch_up_missed: false changes that late-run behavior. Review the due time before resuming if an immediate run would be undesirable. Why a Hermes scheduled job runs at the wrong time explains the related clock and catch-up rules.
Does cancelling undo what the job already did?
No. A sent message, changed remote record or written file can remain after the run stops. Cancellation also cannot reclaim model usage already incurred. Before retrying a job that writes or sends, inspect the actual destination to avoid repeating a partially completed action.
Read three things together: the execution’s terminal status, the job’s scheduling state, and any external result. A cancelled row answers how the run ended; it does not establish that every earlier action was rolled back. If the history still shows an active run, keep the distinction between “requested” and “stopped” visible when asking for help.
Closing your chat terminal is a separate action: accepted work can continue after the terminal closes. Use the job’s own cancellation control when you intend to stop that work.
Vavio supplies a managed remote Hermes computer for $14.99 per month, with model usage billed separately. Hosting lets you leave your own laptop behind; checking a stuck job still means inspecting its run and result. See the current hosting offer, or use these upstream controls on your own server if you prefer to maintain it yourself.
Sources
- Hermes v0.23.1 cron lifecycle and stopping a run, checked 15 November 2026
- Cancellation requests and recorded outcomes, checked 15 November 2026
- Pause, resume, removal and run bookkeeping, checked 15 November 2026
- CLI cancellation reports a request, checked 15 November 2026
- Vavio hosting offer, checked 15 November 2026
Written by Vavio with AI assistance and checked against pinned official Hermes v0.23.1 documentation and source. This is a source review, not a live cancellation, timing or delivery trial.