Description
An Execute Flow Node is used to immediately execute another Flow. This means that the Entrypoint will not switch to the new Flow. This operation can be compared to a function call. After the target Flow finished executing, the current Flow will continue executing. Cognigy monitors the number of times an Execute Flow Node is triggered without user input. The maximum loop count is set to 4 by default. This value is configurable only for on-premises installations. When a Flow is executed, it will inherit the current Context from the parent Flow. The executed Flow can then make modifications to this Context, and these changes will be available to the parent Flow once the execution of the child Flow is completed.Parameters
| Parameter | Description |
|---|---|
| Select Flow | Select the target Flow that is executed whenever the Flow execution triggers the Execute Flow Node. Click  to open the target Flow. |
| Select Node | A Node must be set as an Entrypoint before it can be selected. To set any Node as an Entrypoint, use the Set Entrypoint setting. Select the target Node that executes whenever the Flow execution triggers the Execute Flow Node. |
Advanced
Advanced
Input Object Restoration
When you parse Intents and Slots in a child Flow, the Input Object behaves differently depending on the options you select. If enable both Parse Intents and Parse Slots, most of the Input Object’s properties are restored when you return to the parent Flow. However, the propertiesinputId, execution, and any custom properties added to the Input Object are not restored. For example:
- Parent Flow receives an Input Object with intent A.
- Child Flow parses the input and recognizes intent B.
- Upon returning to the parent Flow, the Input Object will be restored with intent A and any slot values passed from the child Flow.
- Parent Flow receives an Input Object with intent A.
- Child Flow parses the input but does not recognize any Intents or Slots.
- Upon returning to the parent Flow, the Input Object will not be restored and any changes made in the child Flow will not be propagated to the parent Flow.