Skip to main content

Runtime Configuration

Every pipeline has a set of settings that control how it behaves at runtime, independent of what its Workers do:

  • Limit Parallel Runs (limit_parallel_runs) — the maximum number of instances of this pipeline allowed to run concurrently. Use this to prevent overlapping runs of a pipeline that shouldn't execute more than once at a time (e.g. a long-running sync that could conflict with itself if triggered again before finishing).
  • Queue Job Channel (queuejob_channel_id) — which Odoo Queue Job channel batches of this pipeline are dispatched to. Channels let you separate slow/heavy pipelines from fast ones so they don't compete for the same worker capacity.
  • Queue Job Priority (queuejob_priority) — the priority of this pipeline's jobs within its channel; lower numbers run first.
  • Keep Instances For (Days) (keep_instances_for_days) — how long completed pipeline run history (instances, batches, logs) is retained before cleanup, for log-retention and storage management.
  • Log Output (logoutput) — whether pipeline logging is written to the Odoo server logs (odoo_logs) or stored in the database (db), the latter making it queryable/visible from Show Instances.

These settings live on the pipeline form itself (not on an individual Worker), and are generally set once per pipeline based on how critical, frequent, or resource-intensive it is.

Pipeline warnings​

Use Warning, below the pipeline description, to describe consequences that are not obvious from the steps: for example, a mapper that modifies source records. A non-empty warning appears as a yellow banner in the pipeline form and in every instance form. Clearing it removes the banner.

Instances show the pipeline's current warning as a read-only field. Rewording the pipeline updates existing instances too; the warning is not a snapshot of what was displayed when the instance started. Changes are tracked in the pipeline chatter.

The warning is informational. It does not block or delay execution and does not require confirmation. For runs started from a zSYNC UI button, the same warning appears as a persistent notification after the pipeline starts; see Trigger Buttons.