The Jobs page
The Jobs page lists every job of jobs.toml, one line per job, grouped by application, with its last run, its schedule and its actions. It is reserved to superusers.
At a glance
Search and filters
| Element | Use |
|---|---|
| Search | Finds a job by its id, its description or a tag. |
| All applications, Any status, Any tag | Narrow the list. Status: Enabled, Disabled, Scheduled (enabled with a next run), Running now, Last run failed. |
| Clear | Resets the search and the filters. |
| N of M jobs | How many jobs the filters leave. |
| + New job | Opens the job editor — see Create a job. |
The search and the filters are kept in the browser from one visit to the next. Two folded panels hold the policies shared by every job: Run history retention (Administration) and Missed schedules (Schedules).
Groups
- Main jobs comes first: the jobs tagged
main, the ones operators run most — the collection of an application, a nightly sync. - Then one group per application, in alphabetical order: a job belongs to the application its tags or its id name (
nomasx1-collect-all→ Nomasx-1); the others go to Framework, last.
A click on a group's title folds or unfolds it.
A job line
| Element | Meaning |
|---|---|
| Id, description | A click on the id opens the job editor. |
| Last run | The state of the last run; a click opens its detail. |
| Schedule | The cron, or Manual only, with the next run. |
| enabled / disabled | A click switches the job's own schedule on or off at once, without reloading the configuration. Run now works either way, and preset schedules are not affected. |
The icons at the end of the line:
| Icon | Effect |
|---|---|
| Run now | Runs the job. When there is something to choose — parameters, step arguments, several steps, a file_load step — it opens Run with parameters first. While the job runs, it becomes Cancel. |
| Edit | Opens the job editor. |
| Clone | Asks for a new id and creates a disabled copy without any schedule: neither the job's own nor its presets'. |
| Export | Downloads a ZIP with the job's jobs.toml entry and a MANIFEST.md. The connectors and queries it uses are not included. |
| Delete | Removes the job from jobs.toml after confirmation. Its run history is kept. |
Run with parameters
The window applies to this run only — jobs.toml is not changed.
| Part | Content |
|---|---|
| Preset | Pick a saved preset and Apply it: the window first goes back to the job's saved values, then applies the preset — as the scheduler does. (pick a preset…) returns to the saved values. Save as preset… saves the window's current state under a name, in jobs.toml. |
| Shared params (apply to every step) | The job's shared parameters, editable for this run. A parameter offered to users shows as a dropdown — its choices may come from a query, such as the applications of Nomasx-1 —, or as checkboxes headed by All when several values are allowed. |
| Steps | One line per step with a checkbox to skip it (All / None); Edit parameters opens a step's arguments. A file_load step gets a file picker — see Steps. |
| Log level | WARNING — warnings + errors only, INFO — row counts + progress markers, DEBUG — full SQL of every query. |
| Run | Uploads the chosen files, then starts the run. |
Several values, several runs. A job built to run per value — per application, per company — runs once for each value ticked, one run after the other, each with a single value; a failed value does not stop the next ones. All takes every value offered. In Job Runs, each run shows the value it ran for.
Typical uses: rerun only the step that failed, load one month again, run with DEBUG to see the SQL, run a preset by hand, collect three applications in one go.
Cancel
Cancel asks the run to stop. SQL, HTTP, file-load and async Python steps stop at once; the run ends CANCELED. A synchronous Python function cannot be interrupted: the run is marked cancelled and the function finishes on its own — see Troubleshoot.