You signed in with another tab or window. Reload to refresh your session.You signed out in another ta
10BC8
b or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
cron: configurable retry policy for failed runs #115
A failed cron run is never retried; it waits for the next scheduled tick. CronConfig (crates/jiji-config/src/schema.rs) has schedule, command, timezone, timeout, overlap, and missed_runs, with no retry setting, and the agent scheduler has no retry path. This is a feature addition, not a defect: the website documents "Failed runs do not retry automatically."
Scope
A configurable retry policy per job (e.g. attempt count and backoff).
Record each retry as its own run with a distinct cause (scheduled, manual, retry), visible in jiji service cron status/logs.
Define how retries interact with overlap: forbid and the next scheduled tick.
Done when
The cron reference on the website ("Current Limits") and crates/jiji-config/src/jiji.yml are updated in the same change.
Activity