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
..
developer-guide	fix(cron): raise default pre-run script timeout from 120s to 1h (#55489)	2026-06-30 01:00:39 -07:00
getting-started	docs: create dev venv outside the source tree (root-cause fix for #7779) (#54862)	2026-06-29 10:00:37 -07:00
guides	docs: reconcile docs with code across last 3 releases (#54254)	2026-06-28 12:47:50 -07:00
integrations	feat(providers): remove google-gemini-cli + google-antigravity OAuth providers (#50492)	2026-06-21 19:53:27 -07:00
reference	fix(cron): raise default pre-run script timeout from 120s to 1h (#55489)	2026-06-30 01:00:39 -07:00
user-guide	fix(cron): raise default pre-run script timeout from 120s to 1h (#55489)	2026-06-30 01:00:39 -07:00
index.mdx	feat(docs): clarify platform support	2026-06-26 11:37:56 -07:00
user-stories.mdx	docs(website): add User Stories and Use Cases collage page (#18282)	2026-04-30 23:56:59 -07:00