Schedules

Run agents on a schedule or once at a set time.

Schedules start agent runs automatically. Industric checks permission before each run. Pausing or deleting an agent stops future scheduled runs.

Set a schedule

Open an agent's Schedule. Enter a phrase, cron expression, or one-time timestamp, and optionally a timezone. Turning it off clears the schedule; you can still run the agent manually.

Operator support

Schedule edits need the operator's set-agent-schedule capability. If an older operator rejects the edit, upgrade it and retry.

Phrases

Industric converts supported phrases to cron. Unrecognized phrases return an error with examples.

Phrase	Cron
`every minute`	`* * * * *`
`every 15 minutes`	`/15 * * *`
`hourly`	`0 * * * *`
`daily at 9am`	`0 9 * * *`
`weekdays at 07:30`	`30 7 * * 1-5`
`every monday at 6pm`	`0 18 * * 1`
`weekly`	`0 0 * * 1`
`monthly at noon`	`0 12 1 * *`

Also supported: midnight, noon, every weekend, every tue, and fridays. A time alone, such as 9am or 17:45, means daily.

Cron and one-time runs

Cron: use five fields or @daily/@hourly. Set the timezone field or a CRON_TZ=/TZ= prefix. Cron and phrase schedules default to UTC.
One-time run: enter an RFC 3339 timestamp.

In YAML

Set spec.wakeup on the Agent resource:

agent.yaml· yaml

1spec:
2  wakeup:
3    enabled: true
4    mode: schedule          # interval | schedule | oneShot
5    schedule: "0 9 * * 1-5"
6    timezone: Europe/Amsterdam
7    jitter: 30s
8    concurrencyPolicy: Forbid   # Allow | Forbid | Replace
9    activeDeadlineSeconds: 3600
10    backoffLimit: 2

concurrencyPolicy allows, skips, or replaces overlapping runs. activeDeadlineSeconds limits run time. jitter spreads start times across agents.

Run checks

Industric blocks scheduled runs for deleted, paused, or run-disabled agents, even if the cluster has an older configuration. If the operator cannot get a decision, it skips the run.

Pause an agent

Setting Paused removes the resident pod and stops scheduled runs.

Audit log

Each check records agent.schedule.fire.allowed or agent.schedule.fire.denied, with the agent, namespace, deployment, scheduled time, trigger, and denial reason. Review or replay the run in Sessions.