Schedules
A schedule deploys a solution, sequence, or action at a future time — once, or on a repeating cadence. Schedules are managed separately from ad-hoc deployments: you create a schedule, and Mantis creates the deployment for you when it comes due.
Schedules live under Schedules in Lens.
Creating a schedule
Section titled “Creating a schedule”A schedule needs a target to deploy and a time to deploy it.
| Field | Notes |
|---|---|
| Name | Identifies the schedule in lists and audit entries |
| Target | Exactly one of a solution, a sequence, or an action |
| Version requirement | Optional. Pins which version is deployed when the schedule fires |
| Environment | Optional. Scopes the deployment to one environment |
| Scheduled time | The first (or only) run |
| Time zone | An IANA name such as America/New_York. Defaults to UTC |
| Recurrence | Leave empty for a one-time schedule |
The deployment configuration you set on the schedule — execution mode, variables, and the rest — is stored with it and applied to every deployment the schedule creates.
Time zones
Section titled “Time zones”Times are interpreted in the schedule’s own time zone, not the server’s, so a schedule set for 02:00
in Europe/Berlin runs at 02:00 Berlin time year-round and shifts with daylight saving. If the time
zone is missing or unrecognised, Mantis falls back to UTC and records that it did.
Recurrence
Section titled “Recurrence”A schedule with no recurrence runs once and stops. Otherwise it repeats:
- Daily
- Weekly
- Monthly
- Yearly
An optional end date stops the recurrence after a given point. Each schedule tracks when it last ran, when it will next run, and how many times it has executed.
Enabling and disabling
Section titled “Enabling and disabling”A schedule can be disabled without deleting it. A disabled schedule keeps its configuration and history but is skipped when it comes due; enabling it resumes the normal cadence.
Running a schedule immediately
Section titled “Running a schedule immediately”Execute now triggers a schedule’s deployment straight away. This does not consume or shift the scheduled run — the next scheduled execution still happens as planned.
Deployment freezes
Section titled “Deployment freezes”Schedules honour deployment freezes. If a freeze covers the schedule’s scope when it comes due, the deployment is not created. If Mantis cannot determine the freeze state, it declines to deploy rather than risk deploying into a freeze.
How schedules run
Section titled “How schedules run”Mantis checks for due schedules every 60 seconds, so a deployment starts within about a minute of its scheduled time rather than exactly on it.
When several Mantis instances run together, each due schedule is claimed by exactly one of them before it executes, so a schedule does not fire twice because more than one instance noticed it.
Config as Code
Section titled “Config as Code”Schedules can be defined in a configuration repository alongside your other deployment definitions. A schedule managed by a repository shows as managed in Lens and is edited through the repository rather than the UI. See Config as Code for how managed entities work.
Schedules are available through the REST API for listing, creating, reading, updating, and deleting, plus enable, disable, and execute-now operations. See the API Reference for request and response shapes.