Owners and Run Checks
Who a workflow runs as, what happens when its owner leaves, and why a run is refused
Every workflow has one owner: the person who created it, or who took it over later. A workflow always runs as its owner: it uses the connections lent to it, its owner's secret stores and data tables, and the models your organization allows. That holds for a webhook, a form, a schedule or a colleague pressing Run alike.
Before Every Run
Each run, and each run that continues after an approval or a Delay node, is checked first. It does not start, or does not continue, when:
- the workflow was deleted or archived, or, for a webhook, form, schedule, integration or subworkflow, it is not deployed or switched off. A test run in the builder may run a draft
- the owner is no longer an active member of the organization (see below), or the account or organization is suspended
- the person starting it may not run this workflow: they need to own it or have it shared with them for editing
- a subworkflow is called that does not belong to the calling workflow's owner and is not shared with them for editing
- a connection lent to it belongs to someone who is no longer an active member
- a secret store or data table it uses does not belong to its owner
- a model it uses is switched off in your organization's model settings
- a limit is reached, or, for a run started by hand or one that continues, a step uses AI, image generation or web search and the workspace has no credit left (Billing)
The run then shows the reason. No failure email is sent, because nothing ran.
A connection that is not lent to the workflow, or was removed, does not stop the run up front: the run starts and fails at the step that uses it, and the failure email names the connection.
When the Owner Leaves
When an administrator deactivates or removes the owner, or the directory (SCIM) deprovisions them, their workflows stop running. Nobody may keep using a former colleague's mailbox or CRM through a workflow. The workflows themselves stay:
- They show Needs a new owner in the overview and a banner in the builder.
- Everyone they are shared with keeps their access; people with edit access can still edit them.
- If the owner is activated or restored again, the workflows run again as before.
Taking Over
Someone with edit access opens the workflow and clicks Take over, in the banner or in the workflow's ⋯ menu in the overview. They then become the owner. At that moment:
- the connections the former owner lent to the workflow are removed; connections other people lent stay
- every webhook trigger gets a new secret, so its callers need the new value
- the workflow is switched off
Choose your own connections in the nodes that need them, replace secret stores and data tables of the former owner with your own, and switch the workflow on.
For Administrators
Administrators (and roles with Administer all workflows of the organisation) find Workflows of the organisation in the Users group of the Workflows sidebar. It lists every workflow with its owner, state and last run, and lets you:
- Hand over a workflow to yourself or another member. If the former owner is still a member, they keep edit access.
- Switch off a workflow.
- Delete a workflow, including one whose owner's account no longer exists.
This view never opens a workflow's content; for that, its owner has to share it with you.
When you deactivate or remove a member who owns workflows, the confirmation lists them and lets you pick who gets them. Choose Nobody for now to decide later. When a member is deprovisioned through SCIM, nobody can be asked, so your organization's administrators receive an email with the number of affected workflows and a link to this view.