Is Flow Active
Checks whether a specific Conversational Flow is currently in the flow stack, enabling guard logic to prevent flows from being re-triggered.
The Is Flow Active node checks whether a specific Conversational Flow is currently running (present in the active flow stack). It outputs two branches – Active and Not Active – allowing you to guard against re-triggering flows that are already in progress.
Available in: Handlers.
Configuration
Flow
By default this node checks if any Conversational flow is active. Turn on the "Check specific flows" toggle to select which specific Conversational Flows to check. The dropdown lists all flows in the current pipeline. Multiple flows can be selected.
Example use cases
- Prevent greeting re-trigger – In the
On face-detectedhandler, check if theGreetflow is already active before activating it again - Guard against duplicate activations – Before activating a flow via
Activate Flow, confirm it's not already running - Context-aware routing – Route differently depending on whether the user is currently in a specific flow (e.g., mid-checkout vs. browsing)
- Prevent disturbing important flow – Skip continuing processing on an incoming trigger if a high-stakes flow that shouldn't be interrupted is currently active.
Output Ports
| Port | Fires when |
|---|---|
| Active | The selected flow(s) is/are in the current flow stack |
| Not Active | The selected flow(s) is/are not in the flow stack |