FAQ & Troubleshooting
Common questions about templates themselves. Questions about chaining templates together into a multi-step run belong to the Flow Pipelines guide, not this one.
Scope & Targeting
What happens if the node my template points to gets deleted?
A template's scope is pinned to the exact node, thread, or workflow it was created from — it doesn't automatically re-target itself if that node is later removed or the workflow changes shape. Executing the template will fail explicitly with an error rather than silently running against something else. If this happens, the template needs to be re-scoped manually — usually easiest by creating a fresh template from the node's current replacement.
Why did my template's data not show up right after Add?
The new item follows a fixed fallback order — the Templates tab's Item pattern if one is set, otherwise the first existing item stripped of its values, otherwise a blank item. If your grid was empty and no Item pattern was set, a completely blank item is expected. See Data Items Tab for the full rule.
Sharing & Access
Can two people edit the same template at once?
Nothing in the editor actively locks a template while someone else has it open — it behaves like most other configuration screens in the platform, where the most recent save wins. If you're working on a template that others on your team also touch regularly, it's worth coordinating with them before making changes, the same way you would for any shared configuration.
Who can see and run a template someone else created?
Templates are shared across every app in your tenant, not locked to the app that owns the underlying workflow. Anyone with the same access rights as the underlying Process, Thread, or Node can find it in Jobs and run it — creating a template doesn't restrict it to just its creator.
Does Execute check my permissions, or the permissions of whoever created the template?
Access is checked when the template is created — the creator's rights at that moment. It is not re-checked against whoever clicks Execute later. This is a deliberate, known tradeoff: a template shared with someone who doesn't personally have direct execute rights on the underlying node or workflow can still run it through the template, because the check already happened at creation time.
Execution
Why is my Execute button showing an "already running" message?
This template's Concurrency Behavior is set to Block on the Basics tab, and a previous run of this same template hasn't reached a finished state yet. Wait for it to complete (check the Observer Panel, or the Last Executed column in Jobs) and try again, or switch the template to Allow on the Basics tab if overlapping runs are actually fine for this one. See Executing a Template.
Is my template's JSON checked against what the node actually expects before I save?
No. The Configuration saved by a template is free-form JSON — the editor catches syntax errors (malformed JSON), but it doesn't validate that the fields match what the target node actually needs. A template that's well-formed but has the wrong fields will save without complaint and only surface as a problem the next time it's executed.
Attachments
Why does the editor say a file "will be uploaded separately" instead of just attaching it?
Small attachments are stored directly inside the item. Anything larger than roughly 1 MiB is uploaded through the regular document upload flow instead, and the item keeps a reference to it rather than the file itself — this keeps the template's saved data from becoming huge. The message is just letting you know which path a given file is taking.