Cron scheduling overview
Cron is Arinova’s time-driven automation for one-time and recurring jobs. Use the canonical arinova.cron.schedule action. A result with status: active means the job is effective; create and update never wait for a second domain confirmation, while dry-run never persists.
Omitting target wakes the current Agent. The other closed targets post to a conversation, start a Workflow, create an in-app notification, queue outbound delivery, or call an allowlisted action. Web/API v1 may leave Workflow, notify, and outbound jobs Agent-less; action calls remain Agent-bound. Deprecated schedule_message is compatibility-only and points to schedule.
Registry actions (10): schedule, deprecated schedule_message, list_jobs, list_fires, get_job, update_job, set_enabled, cancel_job, run_now, and runtime-only record_run_result. list_fires pages history. Confirmed run_now executes active or paused jobs without advancing schedule or run count. Action results and persisted state are authoritative.
Agents need canCreateCron plus per-job read/write grants. A bound Agent and Agent creator keep a write floor. Agent-less jobs have no floor grant; the owner may grant access in Office. Replacement copies grants and floors a newly bound owned Agent. New user-created jobs never fan out to every Agent.
Related actions
Section titled “Related actions”arinova.cron.schedule, arinova.cron.schedule_message, arinova.cron.list_jobs, arinova.cron.list_fires, arinova.cron.get_job, arinova.cron.update_job, arinova.cron.set_enabled, arinova.cron.cancel_job, arinova.cron.run_now, arinova.cron.record_run_result
Also known as
cron, scheduled job, timed reminder, recurring task, one-time task, agent wakeup
Build a7f47a5ca54ddcf7806cd48b81ce1b9827042766