cron

Cron scheduling for autonomous rover loops is managed through CronCreate and CronDelete lifecycle operations that maintain appropriate firing cadence. The system enforces durable loop state and safety guards to ensure timely checks during standby-heavy missions.

Exponential backoff during idle rover missions slows cron activity when the field goes quiet, applying threshold-based safety guards. It halts scheduling after sustained standby periods and restores normal cadence upon receiving new input.

Yes, cron state can be restored after a session restart using per-loop durability and session restoration logic. This recovers the active cron_job_id from the loop state to resume scheduling without losing progress.

The best way to auto-stop cron activity during sustained standby is through exponential backoff thresholds with safety guards. This logic automatically halts CronCreate cycles to prevent unnecessary firing when rover input remains quiet.

Initialization requires creating the first CronCreate for the active loop and writing the initial cron_job_id to the loop state. The system is loaded by rover, wake, and stop cycles rather than being user-invocable directly.