Module cron
Modules§
Structs§
Enums§
Functions§
- add_
agent_ job - add_job
- add_
once - add_
once_ at - add_
once_ at_ validated - Create a one-shot validated shell job at an absolute timestamp.
- add_
once_ validated - Create a one-shot validated shell job from a delay string (e.g. “30m”).
- add_
shell_ job - add_
shell_ job_ with_ approval - all_
overdue_ jobs - claim_
job - clear_
stale_ locks - deserialize_
maybe_ stringified - due_
jobs - get_job
- handle_
command - list_
jobs - list_
jobs_ by_ agent - Cron jobs owned by
agent_alias, for the agent-deletion export-then-delete archive - list_
runs - next_
run_ for_ schedule - normalize_
expression - parse_
delay - pause_
job - record_
last_ run - record_
last_ run_ with_ status - record_
run - release_
job - remove_
job - remove_
jobs_ by_ agent - Delete every cron job owned by
agent_alias, returning the row count (cron_runscascade via theirjob_idFK). A job whose owning agent is gone can never run, so the agent-deletion cascade removes it - rename_
jobs_ by_ agent - Re-point every cron job owned by
fromtoto, returning the row count. Called by the agent-rename cascade the job keeps running, just under the renamed owner.agent_aliasis plain TEXT (not a UUID), so this is a direct column update. - reschedule_
after_ run - reschedule_
after_ run_ with_ status - resolve_
job_ id_ or_ name - resume_
job - schedule_
cron_ expression - skip_
missed_ run - sync_
declarative_ jobs - update_
job - update_
shell_ job_ with_ approval - Update a shell job’s command with security validation. Validates the new command (if changed) against the named agent’s risk profile before persisting.
- validate_
delivery_ config - validate_
schedule - validate_
shell_ command - Validate a shell command against an agent’s security policy
(allowlist + risk gate).
agent_aliasnames the agent under whose risk profile the command will run. ReturnsOk(())if the command passes all checks, or an error describing why it was blocked. - validate_
shell_ command_ with_ security - Validate a shell command using an existing
SecurityPolicyinstance. Preferred when the caller already holds aSecurityPolicy(e.g. scheduler).