Skip to content
vavio

Hermes restarted in the middle of my request. Will it resume, or answer twice?

If Hermes restarts while it is working on your request, the interrupted task is not run again, and Hermes will not finish it on its own when it comes back. Your conversation and the messages queued behind it are kept. Ask Hermes what was already done, then repeat the request. After a crash, Hermes may instead pause the conversation until you send /discard. A reply that was finished but not yet sent is delivered rather than regenerated. If Hermes cannot be sure the platform received it, the reply is marked as a possible duplicate.

This follows Hermes Agent v0.23.1, commit 3b42157, checked on 17 November 2026. It covers chats through Hermes’s messaging gateway, such as Telegram, Discord or Slack. We reviewed official documentation and source. We did not restart or crash Hermes during a task on a Vavio computer for this article.

What happens to the task that was running?

It depends on whether Hermes stopped cleanly.

A planned restart or shutdown, such as an update or hermes gateway restart, interrupts a running chat turn straight away by default. The setting is agent.restart_drain_timeout, and its default is 0. Before going down, Hermes posts a notice in chats with a running task, and usually in each home channel, unless gateway_restart_notification: false turns that off:

⚠️ Hermes is restarting — your current task will be interrupted. Send any message after the restart and I’ll try to resume where you left off.

Don’t read “resume” as “finish the task”. The upstream configuration guide states the result plainly: the interrupted turn “settles as interrupted and is never run again”, and you send the request again once Hermes is back. Messages queued behind it are kept and run in order on the new gateway.

A crash, or a process killed in the middle of a turn, leaves Hermes unable to prove which actions already happened. It marks that turn as lost, neither replays it nor runs the messages queued behind it, and pauses the conversation. Your next message is saved, and Hermes replies:

⏸️ This conversation is paused: a previous turn did not finish when Hermes restarted, and only you know whether to send it again. Your message is saved. Send /discard to drop the lost turn and continue (it is not re-run), or /reset to start a fresh conversation.

/discard records the lost turn as interrupted, and your saved messages are then answered in order. On Slack, use /hermes discard. /reset starts a fresh conversation, leaving the lost turn and its saved messages in the old one.

Why Hermes does not simply carry on

A task can be cut off after some of its actions have already happened. A file may already have been written, an email sent or a command run. Re-running the whole turn automatically could repeat those effects. That is why Hermes leaves the decision to you.

So before you repeat a request, ask Hermes what it had already done. For example:

You were interrupted by a restart while sending the weekly invoices. Check which invoices were already sent, tell me, and don’t send anything yet.

Then decide what still needs doing.

Will I get the same answer twice?

Hermes keeps a delivery ledger of final replies around each platform send:

When the gateway went down What happens after it is back
The reply was recorded for sending, but the send had not started It is delivered as it is. The turn is not regenerated
The reply was being sent, or was finished but not yet recorded for sending It is redelivered with “♻️ Recovered reply — the gateway restarted during delivery, so this may be a duplicate”
The turn had already finished and its reply was delivered Nothing. A recently active chat is not answered again

Similar “Recovered reply” labels appear when a platform refused or rate-limited the original send. Redelivery is bounded to three attempts and 24 hours. The ledger can be turned off with gateway.delivery_ledger: false, in which case a reply that was in flight during a crash is lost.

So a duplicate is possible, but Hermes labels the ambiguous case rather than silently resending. If you see a recovered reply, check whether you already have it before acting on it twice.

What if I message Hermes during the restart?

Hermes may reply “⏳ Hermes is restarting — your message is saved and will be answered when it is back.” We have not tested which reply you get on each platform, so check that your message was answered once Hermes is back, and resend it if not. How Hermes treats a message sent while it is busy, rather than restarting, is covered in what happens if you message Hermes while it is still working.

Scheduled jobs are handled separately. A job cut short by a restart produces no result for that run, and Hermes says it will run again on schedule. The scheduled-job restart guide covers catch-up and replay.

Can I make restarts wait for my task?

Yes. Set agent.restart_drain_timeout to a number of seconds to let running turns finish before Hermes stops:

agent:
  restart_drain_timeout: 60

Every restart and update then waits up to that long. On a systemd service, re-run hermes gateway install after raising it, so the service’s stop timeout grows to match. Otherwise the service manager can kill the gateway in the middle of its drain, which leaves the turn lost as in a crash. On macOS, launchd caps the stop timeout at 60 seconds. A turn that is still running when the drain ends is interrupted as above.

What hosting changes

Any Hermes installation restarts sometimes, for an update, a configuration change or a crash. That includes managed ones. Vavio supplies a managed Hermes computer for $14.99 per month, with model usage billed separately. It looks after the computer and Hermes. It does not change how Hermes treats a turn cut off by a restart. Check what was done, then ask again. Review the current hosting offer if that is the service you need.

Sources

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 restart, crash or delivery trial.

More from the Vavio blog: Hermes Agent guides