On this page
Why Flow activation can fail
This article discusses common reasons for Flow activation failure, including issues with the Gateway Steps, duplicated URL paths, and invalid JSON files. It provides solutions to address these problems and ensure a successful Flow activation.
Common issues that will prevent you from activating your Flow include:
An invalid or empty Trigger field in the Gateway Step (like an invalid/empty URL path field in the Wait for HTTP Request Step). Verify any missing Step template configurations by checking the Details tab.
The same URL path for different Flows. When working with a Flow copy, make sure this parameter is unique for each Flow. If it is an RWC Flow copy, remove the existing Gateway Step and replace it with a new one from the Library. This action guarantees that the unique URL is regenerated randomly, preventing interference with the original Flow.
An invalid JSON file in the Flow source. In case you have made changes to the Flow source, validate the JSON to catch any syntax errors.
Missing Gateway Step. Without the Gateway Step, the Flow will not function, as there is no way for it to start executing.
The Flow's trigger already exists within the current account (e.g., an inbound Voice Flow is active with the same identifier already in use). In this case, you will receive an activation fail notification with the link to the Flow that prevents the activation. To resolve this issue, update the trigger or deactivate the conflicting Flow.
An empty Bot identifier for inbound/outbound SMS/Voice Flows (when the first Step on the tree isn't the Gateway Step, etc.).
NPM version in Flows and Steps.
Follow this article on how to debug your Flows.
Flows that are Deleted stop new flows with the same 'Custom Trigger Name' from being activated. (Must fully delete the deleted flow to activate the newer flow of the same trigger name).