Skip to content
vavio

Why does my Hermes scheduled job run at the wrong time?

A Hermes Agent scheduled job usually runs at the wrong time because its schedule is being read in a different time zone from the one you meant. With no time zone configured, Hermes reads a job’s schedule in the server’s own clock zone. Many cloud servers keep their clock on UTC; on one of those, “every day at 9am” fires at 09:00 UTC. Set timezone in the profile’s config.yaml, or pin the job to its own zone, then check the job’s next run time.

This answer follows Hermes v0.23.1, commit 3b42157, checked on 15 November 2026. We reviewed official source and documentation; we did not run a scheduling or timing trial on a Vavio computer.

Which time zone does a Hermes job use?

Hermes picks the first of these that is set:

Order Setting Applies to
1 The job’s own timezone, for example --timezone Europe/London That job’s recurring schedule
2 timezone: in the profile’s config.yaml The profile’s clock and every job without a pin
3 Nothing set: the server’s local time Everything

A HERMES_TIMEZONE environment variable can also set the zone for a one-off command, but the gateway that runs scheduled jobs replaces it with the profile’s timezone when that is set. Set the profile value rather than the variable.

The same zone sets the date and time zone Hermes sees in its own system prompt, so a Hermes that thinks it is a different time from you is a sign of the same mismatch. The setting does not change log files, which keep the machine’s local time.

Use an IANA zone name such as America/New_York, Europe/Berlin or Asia/Kolkata, not an abbreviation such as EST. A job’s pinned zone is checked when you set it, and an unknown name is refused. A misspelled profile timezone, such as Asia/Tokio, is not: Hermes logs a warning and quietly falls back to the server’s time. hermes doctor reports that mistake.

How do I check what a job will do?

Run hermes cron list in a terminal on the Hermes computer, or ask Hermes in chat to list its scheduled jobs. Three rows tell you most of what you need:

  • Next run is a full timestamp with its UTC offset, such as 2026-11-16T09:00:00+00:00. The offset shows which zone the time was calculated in. +00:00 on a job you meant for New York means it is running on UTC.
  • Timezone appears only when the job has its own pinned zone.
  • Dispatch compares the last scheduled time with when the job actually ran, and labels it on time, late, or a catch-up after a missed run.

If the row reads Overdue instead of Next run, the scheduled time is more than 15 minutes past and the job has not fired, so the scheduler may not be running. That is a different problem from a time zone; does closing my terminal stop Hermes? covers it.

Is it the wrong zone or a late run?

The two look similar from a chat window. Tell them apart before changing anything:

What you see Likely cause What to check
The job fires at the same wrong hour every day, a whole number of hours off Wrong time zone The UTC offset on Next run against your own offset
The hour was right until a daylight-saving change, then moved by one hour An interval schedule such as every 24h, not a daily time The job’s Schedule row
The job ran once, much later than scheduled, after the computer was off or the gateway stopped A catch-up run The Dispatch row says late or catch-up
Nothing arrives at all The job did not run, or delivery failed Next run says Overdue, or hermes cron doctor reports a delivery failure

How do I fix it?

  1. Set your zone for the whole profile. Run hermes config set timezone Europe/London on the Hermes computer, or ask Hermes to run that command for you. Hermes reads the zone once when it starts, so restart the gateway afterwards. Existing jobs keep the Next run already on file. When that moment arrives, Hermes moves a job that would now fire early to your new local time, and a job that is now late fires once and then follows the new zone. To skip that transition, re-save each job’s schedule (hermes cron edit <job> --schedule "every day at 9am") after the restart and check its Next run.
  2. Or pin one job to its own zone. Run hermes cron edit <job> --timezone America/New_York, or ask Hermes to change the job’s time zone. Hermes recalculates the next run straight away. This suits a profile that serves several places, such as a market-open brief for each city. Pass --timezone "" to go back to the profile’s zone.
  3. Use a daily time, not an interval, when the hour matters. every day at 9am, weekdays at 9am and the cron expression 0 9 * * * stay at 09:00 in their zone across daylight-saving changes. every 24h or every 1d counts elapsed time from the job’s last run. It has no wall-clock hour, so it moves by an hour when the clocks change, and a pinned zone has no effect on it.
  4. Give one-off reminders an offset or a delay. A timestamp without an offset, such as 2026-12-01T09:00:00, is read in the profile’s zone, even on a job pinned to another zone. A timestamp with an offset, such as 2026-12-01T09:00:00-05:00, is already a fixed moment. For “remind me in two hours”, ask for in 2h so Hermes does not have to work out the clock time itself.

When you ask in chat (“every weekday at 8am, summarize my inbox”), Hermes turns that into one of these schedule forms and reads it in the zone it resolves. Setting the profile zone first means “8am” means your 8am.

What happens when the clocks change?

A daily or weekly time stays on the wall clock: a 09:00 job runs at 09:00 local time before and after the change. The Hermes source handles the repeated hour in autumn so the next run is never calculated in the past. A time inside the hour the clocks skip in spring has no exact match on that day, so avoid scheduling jobs in the hour your zone changes (often between 01:00 and 03:00), or check that day’s Next run.

Why this comes up when Hermes moves to a cloud computer

A Hermes on your laptop inherits your laptop’s time zone without any setting. Moved to a cloud server, it inherits the server’s zone, and jobs created earlier keep running on that clock. The fix is the profile timezone setting above, not a different server.

Recurring jobs are the main reason to keep Hermes on a computer that stays online, because they run while your own computer is off. Vavio gives your Hermes its own managed computer for $14.99 per month, with model usage billed separately by your provider. Hosting keeps the scheduler running; the job’s time zone is still a Hermes setting you choose. Compare the current hosting offer with running Hermes yourself.

Sources

Written by Vavio with AI assistance and checked against pinned official Hermes v0.23.1 source and documentation. This is a source review, not a live scheduling or timing trial.

More from the Vavio blog: Hermes Agent guides