Article content
If a flow in Flows Building triggers successfully but one or more actions fail, the issue is usually related to configuration, data, permissions, or external systems.
This article explains the most common reasons actions fail and how to identify and resolve them.
Confirm the Flow Triggered
Before troubleshooting actions, confirm that:
-
The flow did trigger
-
The failure occurred after the trigger
-
The correct flow version is published
If the flow did not trigger at all, see Troubleshooting Flows That Are Not Triggering.
Check Action Configuration
Actions require specific configuration to run successfully.
Check that:
-
All required fields are completed
-
Field values are mapped correctly
-
Data types and formats match expectations
Missing or incorrect configuration is one of the most common causes of action failures.
Validate Input Data
Actions often rely on data passed from earlier steps.
Common data issues include:
-
Empty or null values
-
Unexpected formats (for example text instead of numbers)
-
Fields that only exist in certain scenarios
Ensure that data is present and valid before the action runs. Adding conditions earlier in the flow can help protect actions from invalid input.
Review Action Order
Actions run in the order they are connected.
Check whether:
-
An action depends on output from a previous step
-
Required data is generated before the action runs
-
Actions are placed after any necessary conditions
Incorrect ordering can cause actions to fail even when configuration appears correct.
Check Permissions and Credentials
Some actions require specific permissions or credentials.
Failures may occur if:
-
Credentials have expired or been revoked
-
Access permissions have changed
-
The action is attempting to perform an unauthorised operation
Confirm that any required credentials are current and have the necessary access.
Consider External System Availability
Many actions interact with external systems.
Action failures can occur if:
-
The external system is unavailable
-
Rate limits are exceeded
-
The external service returns an error
Temporary failures may resolve once the external system recovers.
Review Recent Changes
If actions previously worked and now fail:
-
Review recent edits to the flow
-
Check for changes to credentials or permissions
-
Confirm the flow was republished after updates
Recent changes are often the root cause.
Test Actions in Isolation
To isolate the problem:
-
Temporarily simplify the flow
-
Trigger the action with known good data
-
Remove unrelated actions
This approach helps identify whether the issue is with the action itself or earlier logic.
When to Contact Support
Contact Pickle Support if:
-
Actions continue to fail despite correct configuration
-
Failures occur intermittently without a clear cause
-
You need help interpreting errors or behaviour
When contacting support, include:
-
The flow name
-
The action that failed
-
What you expected the action to do
-
What actually happened
-
Approximate time of the failure
Providing this information helps speed up resolution.
Related Articles
-
Troubleshooting Flows That Are Not Triggering
-
Understanding triggers, conditions & actions
-
Editing, versioning & publishing flows
-
Common mistakes when building flows