FAQ & Troubleshooting
Answers to the questions that come up most once you start building real Pipelines.
Running & Concurrency
Can I run the same Pipeline twice at once?
Yes. Clicking Execute always starts a brand-new, independent run — there's no locking that blocks a second run while a first one is still going. Each run gets its own entry in the run-history list and steps through its own items separately from any other run of the same Pipeline. This matches how the plain Execute button on a single Template already works today.
Can two Pipeline steps use the same underlying workflow?
Yes, with no conflict. Each step in a Pipeline produces its own independent execution when it runs, even if two steps happen to point at Templates built on the same workflow. There's nothing to coordinate between them — they simply run as two separate, unrelated executions.
Templates & Configuration
What happens if I edit a Template that's already used in a Pipeline?
Nothing changes in the Pipeline automatically. As explained in Adding Items & Template Lookup, each Pipeline step keeps a frozen snapshot of the Template's Configuration taken when the step was added (or last refreshed). Editing the Template afterward doesn't reach into any Pipeline already using it — the step keeps running its own snapshot until someone opens that step and clicks Refresh from template.
Why doesn't my Configuration Override show up in the run right away?
Overrides are also folded into that same frozen snapshot at the moment you set them, not applied live at run time. If you change an override after the step was added, click Refresh from template to re-freeze the snapshot with your latest override applied.
Failures & Timeouts
A step "failed" but the underlying workflow actually finished fine later — why?
This usually means the step didn't reach a finished state within the Pipeline's configured wait time (set in Creating a Pipeline, default 1800 seconds). When that window elapses, the Pipeline treats the step as failed and applies its On-Failure Behavior, even if the underlying execution eventually completes on its own afterward. If your steps routinely run long, raise the Pipeline's wait-time setting.
My Pipeline stopped early even though I set some steps to Continue — why?
Check the On-Failure Behavior of the specific step that failed, not the others around it. Each step has its own independent setting — a Stop-behavior step earlier in the list will still halt the run even if every other step is set to Continue or Skip.
Scheduling
Can I schedule a Pipeline to run automatically?
Not yet — today a Pipeline runs only when you click Execute, either from the builder screen or the search screen's row action. Automatic, schedule-driven triggering is planned for a later phase and isn't available in this release.