Help

Hermes gateway not running: why schedules, kanban and bots stall

Herald talks to hermes serve, but some Hermes Agent work happens in a separate process, the messaging gateway. It runs cron jobs, starts kanban cards through its dispatcher, delivers results into Bot Chats and connects Telegram and other messengers. If it stops, Herald can still chat, but schedules don’t fire and Ready cards don’t start. Check it with hermes gateway status.

What stops without the gateway

Hermes Agent features that need the gateway, as you see them in Herald
In HeraldWith the gateway stopped
SchedulesJobs don’t fire, and a Bot Chat delivery to a profile whose gateway is down is recorded as failed
KanbanReady cards stay in Ready, because the dispatcher runs inside the gateway
Bot listBots running under another profile can be missing if the default profile’s gateway is stopped
Telegram and other messengersYour bots stop answering there
Chatting in HeraldStill works, through hermes serve

Check and start it

  1. See what is running

    hermes gateway status shows the gateway for the current profile; hermes gateway list shows every profile and whether its gateway is running.

    hermes gateway status
    hermes gateway list
  2. Start it

    Use hermes gateway start if it is installed as a service, or hermes gateway run to run it in the foreground, which the Hermes docs recommend for WSL, Docker and Termux.

    hermes gateway start
  3. Keep it running

    hermes gateway install sets it up as a systemd service on Linux or a launchd service on macOS, so it survives restarts. On WSL, run hermes gateway run inside tmux instead.

  4. Check the scheduler

    This says whether cron is alive, when it last ticked and when the next job is due.

    hermes cron status
  5. Read the log if it won’t start

    hermes logs gateway shows platform connections and errors.

  6. Refresh Herald

    Pull down on the roster, and reopen Schedules or the kanban board.

hermes serve and the gateway are different

Herald connects to hermes serve, the backend Hermes Desktop also uses, on port 9119. The messaging gateway is a separate background process that connects your messaging platforms, handles their sessions, runs cron jobs and delivers voice messages. The two run side by side, and npx herald-setup only starts hermes serve.

After it’s back

A recurring job that missed its time while the gateway was down runs once when the scheduler returns, however long the gap. Paused jobs never catch up. Bot Chat deliveries that failed aren’t sent again automatically, but the output stays in hermes cron runs. Ready kanban cards are picked up on the dispatcher’s next pass, every 60 seconds by default.

Questions

Do I need the gateway if I only use Herald?

For chatting, no. For schedules, kanban runs and Bot Chat deliveries, yes.

Does npx herald-setup start the gateway?

No. It starts hermes serve when nothing answers, which is what Herald connects to. Start the gateway separately.

My computer went to sleep. Will jobs run?

Not while it sleeps. When it wakes and the gateway is running again, each recurring job that missed its slot runs once.

Sources

Get Herald for Hermes Agent

iPhone, iPad, Apple Watch, CarPlay and Android. $12.99 once, no subscription, no account and no Herald server.

Herald is an independent, unofficial app. It is not made, endorsed or supported by Nous Research.