Article content
If a flow in Flows Building is not triggering, it usually means a configuration or logic condition is preventing it from starting.
This article helps you identify the most common reasons a flow does not trigger and what to check before contacting support.
Start With the Basics
Before diving deeper, confirm the following:
-
The flow is published
-
The triggering event has actually occurred
-
The flow is enabled and not paused or unpublished
If any of these are not true, the flow will not run.
Check the Trigger Configuration
Triggers define when a flow starts. If the trigger conditions are not met, the flow will not trigger.
Check that:
-
The correct trigger type is selected
-
Trigger conditions match the event you expect
-
Required trigger fields are populated
-
Values are not too restrictive or too broad
Even a small mismatch can prevent the trigger from firing.
Confirm the Triggering Event Occurred
Flows only trigger when the defined event happens.
Ask yourself:
-
Did the event actually occur?
-
Did it occur after the flow was published?
-
Is the event type supported by the trigger?
Events that occurred before publishing will not trigger the flow.
Review Conditions Immediately After the Trigger
Conditions placed immediately after a trigger can stop a flow early.
Check whether:
-
Conditions evaluate to false
-
Data used in conditions is present and valid
-
Logic paths are set correctly
If a condition fails, the flow may stop without running any actions.
Look for Missing or Invalid Data
Some triggers rely on data being available at runtime.
Common issues include:
-
Empty fields
-
Unexpected data formats
-
Assumptions about values always being present
If required data is missing, the flow may not proceed past the trigger.
Check Recent Changes
If the flow previously worked and now does not:
-
Review recent edits to triggers or conditions
-
Confirm the flow was republished after changes
-
Check whether permissions or access were modified
Recent changes are often the cause of new issues.
Verify Permissions and Access
Insufficient permissions can affect flow behaviour.
Confirm that:
-
The user who published the flow has the correct access
-
Required system permissions are still in place
-
No access restrictions were introduced
Permission-related issues can prevent flows from running as expected.
Test With a Simple Scenario
To isolate the issue:
-
Temporarily simplify the trigger
-
Remove conditions
-
Test with a known event
If the simplified flow triggers, reintroduce logic step by step to find the cause.
When to Contact Support
Contact Pickle Support if:
-
The flow is published and still not triggering
-
Trigger conditions appear correct
-
Events are occurring as expected
-
You cannot identify why the flow is not running
When contacting support, include:
-
The flow name
-
The trigger type used
-
What you expected to happen
-
What actually happened
-
Approximate time of the triggering event
This information helps speed up investigation.
Related Articles
-
Understanding triggers, conditions & actions
-
Editing, versioning & publishing flows
-
Common mistakes when building flows
-
Managing access & permissions in Flows Building