How-To Guides

Why a Flow Is Not Visible or Not Available to Trigger

Last updated 03 June 2026

Why a Flow Is Not Visible or Not Available to Trigger

If a user cannot see a flow in their list or cannot trigger it, one of the following reasons usually applies. Work through them in order.

Reason 1: The flow is in Draft

A flow must be published before it appears in the /flows trigger list. Draft flows are visible only to admins inside the Flow Builder.

How to check: Open the flow in the builder. The Publish panel in the top-right will show Draft or the current published version number.

How to fix: Click Publish in the Publish panel.

See Flow Draft vs Published for full detail.

Reason 2: Trigger restrictions — user's department is not allowed

A flow can be restricted to specific departments. If the user's department is not on the allowed list, the flow will not appear in their trigger list at all — it is as if it does not exist for them.

How to check: Open the flow builder → Publish panel → Trigger Restrictions section. If departments are listed, only users in those departments can see and trigger the flow.

How to fix: Add the user's department to the allowed list, or move the user to an allowed department.

Reason 3: The user has no department assigned

If a flow has trigger restrictions and the user has no department assigned, they will not match any entry in the allowed list.

How to check: Open the user's profile in Users — look at the Department field.

How to fix: Assign the user to the relevant department via their profile or via the Departments management page.

Reason 4: The user account is deactivated

An inactive (deactivated) account cannot see or trigger any flows.

How to check: Open the user's profile page. An amber Inactive banner appears at the top if deactivated.

How to fix: Click Reactivate on the user's profile page.

Reason 5: The user is looking in the wrong place

Flows available to trigger are listed on the /flows page (accessible from the "Flows" item in the left sidebar). The /tasks page → My Flows tab shows instances the user has already triggered — it does not show flows available to start new ones.

How to fix: Direct the user to the /flows page.

See also