hermes-agent/website/docs/reference
Teknium 643b0dc678
fix(cron): raise default pre-run script timeout from 120s to 1h (#55489)
Cron pre-run scripts were capped at 120s by default, which surprised
users running long data-collection scripts on crons (the whole point of
crons being to offload long work). Raise _DEFAULT_SCRIPT_TIMEOUT to 3600s
(1 hour).

This bounds the script only — skill/agent jobs already run on a separate
inactivity budget (HERMES_CRON_TIMEOUT, default 600s idle, 0=unlimited),
not a wall-clock cap. Scripts dispatch to a persistent thread pool and do
not hold the tick lock, so a long script doesn't starve other due jobs.

Docs clarified to make the script-vs-agent timeout distinction explicit.

env/config overrides (HERMES_CRON_SCRIPT_TIMEOUT,
cron.script_timeout_seconds) unchanged and still take precedence.
2026-06-30 01:00:39 -07:00
..
_category_.json
…
automation-blueprints-catalog.mdx
…
cli-commands.md
…
environment-variables.md fix(cron): raise default pre-run script timeout from 120s to 1h (#55489) 2026-06-30 01:00:39 -07:00
faq.md
…
mcp-config-reference.md
…
model-catalog.md
…
optional-skills-catalog.md
…
profile-commands.md
…
skills-catalog.md
…
slash-commands.md
…
tools-reference.md
…
toolsets-reference.md
…