Executing a Template
Once a template is saved, running it is one click. This page covers what that click actually does, and the one setting that decides whether you're allowed to click it twice.
The Execute Button
Every template has an Execute action — on its row in the Jobs list, and inside the editor itself. Clicking it does not open anything or navigate anywhere: it immediately triggers a run using the scope and data saved on the template, exactly as if you'd opened that node, thread, or workflow yourself and clicked the ordinary Execute button on the canvas.
Click Execute on a template
│
▼
Template resolves its saved scope
(which Process / ProcessThread / Node it targets)
│
▼
Template's saved Data Items become the input
│
▼
Runs exactly like a normal Execute
│
▼
Result is a normal execution — visible in the
Observer Panel like any other runBecause it runs like any other execution, everything you already know about watching a run — the Observer Panel, execution status, node-by-node output — applies here unchanged. A template is a shortcut to starting a run, not a different kind of run.
Concurrency Behavior — Allow vs Block
Set on the Basics tab of the template editor (see The Five Tabs), Concurrency Behavior decides what happens if you (or someone else) click Execute on the same template again while an earlier run of it hasn't finished yet.
| Setting | What Happens | When to Use It |
|---|---|---|
| Allow Default | Every Execute click starts its own independent run, even if a previous run of this template is still going. This matches how the plain Execute button on the canvas has always worked. | Read-only or safely-repeatable actions — running the same report twice at once causes no harm. |
| Block | A click is rejected while a previous run of this same template is still in progress. You'll see a message telling you it's already running instead of a second run silently starting. | Actions where a duplicate run would cause a real problem — for example, a template that sends a payment or creates a record that shouldn't be created twice. |
This is a per-template choice, not a global setting — a read-only reporting template and a payment-sending template can each have the behavior that actually fits them.
The "Already Running" Message
If a template's Concurrency Behavior is set to Block and you click Execute while an earlier run hasn't reached a finished state yet, the click is rejected and you'll see a message telling you the template is already running. This isn't an error in your data — it's the Block setting doing exactly what it's for. Wait for the in-progress run to finish (check the Observer Panel or the template's LastExecutedAt in Jobs), then try Execute again.