Skip to main content

Jobs

App page

Jobs represent a deployment configuration: project + workflow (or pipeline) + environment + (optional) schedule. Scheduled jobs dispatch through the internal queue before the worker executes them, which improves durability, retries, delayed execution, and operational visibility without changing how Job Runs appear in the UI.

Manual canvas runs still execute directly (they don't go through the queue).

In the Jobs list:

  • Project names are hyperlinks to open that project.
  • Workflow / Pipeline labels are hyperlinks that open the project and switch the canvas to the referenced workflow or pipeline.
  • Environment badges are hyperlinks to open the Environments page filtered to that environment.

Create a job​

  1. Click Add Job
    From the Jobs page.
  2. Select Project / Workflow or Pipeline / Environment
    Workflow and Pipeline options are populated from the selected project.
  3. Readiness checks
    Only missing environments and runtimes required by the selected workflow/pipeline block job creation. Connections that are not used in the selected workflow/pipeline do NOT block creation.
  4. Scheduling (optional)
    Jobs can be deployed without a schedule. If scheduling is enabled, configure cadence and start time.
  5. Save
    The job appears in the list. The first scheduled fire (or a manual Run Now) writes a Runtime Execution record.

Cancel / stop a running job​

If a job is executing, use the Cancel / Stop controls where available to request runtime cancellation. Cancellation is best-effort; nodes that are mid-write may complete the row in flight before honouring the signal.