# witcheer's Wingtips #61: cron preflight

Written by [witcheer](https://x.com/witcheer) at Nous Research. Republished with credit.

Canonical: https://hermeswatcher.com/wingtips/61  
Published: 2026-09-02  
[Original](https://notwitcheer.github.io/hermes-recipes/wingtips/61-cron-preflight/) · [On X](https://x.com/witcheer/status/2095028256332271691) · [Full collection](https://notwitcheer.github.io/hermes-recipes/) · [Official docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron#pre-dispatch-configuration-validation)

[Source Markdown](https://raw.githubusercontent.com/notwitcheer/hermes-recipes/8653fb699a137a32e81936fa33cabacd3f4f2095/docs/wingtips/61-cron-preflight.md): use this file as the base for relative links in the verbatim text below.

Sources: [Hermes docs: Cron](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron#pre-dispatch-configuration-validation)


Hermes Wingtips #61: cron preflight

before a scheduled job runs, your Hermes Agent checks that the run can actually succeed: the provider key resolves, attached skills have what they need, delivery targets are reachable.

a job that fails the check is marked blocked_config and alerts you once. no model call happens, so it sits at zero cost until you fix it.

the next healthy run clears the state on its own.