Jobs
Jobs let you schedule when Bragi Configs should run. In this section, you configure the CRON schedule, control the order of Config execution, set dependencies on other Jobs, and more.
To add Configs to a Job, use the search card at the bottom of the Job Edit page to select the Configs you want included. These appear under the Scheduled Tasks tab.
Field | Description |
|---|---|
Name | A descriptive name for the Job (e.g., |
Description | A summary to clarify the Job’s purpose for other users. |
Status | Job state: |
Is Scheduled? | If |
CRON | Defines when the Job will run (see the CRON section below). |
Bragi automatically calculates task dependencies, but you can also manually set dependencies in the Task Maintenance panel.
To set dependencies, click the arrow next to No dependencies. When you select a dependent Job, you can specify whether it must succeed before this Job runs and how recent the last successful run should be.
Behaviour of Missed Runs and Next Run Time Display
If a Job misses its scheduled run due to unmet dependencies, Bragi shows the Job’s next run time as a timestamp in the past, reflecting when the run should have occurred. This can be surprising at first glance.
This behaviour means the Job didn’t run when expected, usually because a dependency wasn’t satisfied in time. Understanding this helps avoid misinterpreting the schedule during monitoring.
CRON Scheduling
Bragi uses the well-known CRON utility to schedule Jobs.
A CRON expression has five fields, in order:
Minute
Hour
Day of the Month
Month
Day of the Week
CRON Examples
Expression | Description |
|---|---|
| Runs every five minutes |
| Runs every hour at 15 minutes past the hour |
| Runs every three hours |
| Runs daily at 1:00 AM |
| Runs Monday through Friday at 8:00 AM |
| Runs at 5:00 PM on the 2nd day of each month |
| Runs at 2:00 AM on the 1st day every 6th month |