Cron jobs

Cron Jobs lets the running gateway invoke a registered tool on a schedule. Use it for bounded recurring checks and local automation—not for an expectation that Ódinn runs while the gateway is stopped.

Create a job

Open Cron Jobs in the console and provide:

• a clear name;
• a five-field cron expression;
• an explicit IANA timezone;
• a registered tool;
• the tool’s structured input.

The console previews the schedule before saving it.

Execution boundary

A scheduled job uses the same:

• forked crash-containment worker;
• policy and capability checks;
• quotas and input limits;
• idempotency behavior;
• audit recording;
• retry-safety classification

as an ordinary gateway task.

Forked workers contain crashes; they are not a security sandbox and retain the parent operating-system user’s authority.

Operational behavior

The gateway evaluates schedules every 30 seconds. It must remain running for a schedule to fire. Use Run now to test a job before relying on its schedule.

Editing or creating a cron job is a privileged control-plane change. Review the selected tool and input as carefully as you would an interactive action.

Safe scheduling guidance

• Prefer read-only or clearly idempotent tools.
• Avoid scheduling browser mutations or irreversible external actions.
• Choose a timezone explicitly; do not assume the host timezone.
• Inspect the resulting task and audit record after the first run.
• Disable a job that repeatedly fails instead of allowing an error loop to accumulate.

For gateway availability problems, see Troubleshooting. For recorded runs, see Tasks and activity.