Q: What causes Flow Designer Subflow Not Passing Variables Correctly?

Output variables not mapped in Call Subflow action — In the parent flow's Call Subflow action, check the Outputs tab. If output variables aren't explicitly mapped to parent flow data pills, they won't be available downstream. Variable type mismatch between subflow and parent — Compare the variable types in the subflow's Output section with the data pills being passed to the parent. Check sys_flow table records for both flows to verify data types match exactly. Subflow completing before async operations finish — Check execution details in sys_flow_context table for the subflow execution. Look for steps completing out of order or async actions (like REST calls) that haven't finished before the subflow returns. Incorrect output variable names in parent flow — In the parent flow, verify the data pill names match exactly with the subflow's defined output variable names. Check the subflow's Output section for the exact spelling and case. Subflow execution failing silently — Check sys_flow_context table for error records related to the subflow execution. Also verify the subflow's error handling isn't swallowing exceptions that prevent proper output generation.

Question 1

What causes Flow Designer Subflow Not Passing Variables Correctly?

Accepted Answer

Output variables not mapped in Call Subflow actionhigh likelihood

In the parent flow's Call Subflow action, check the Outputs tab. If output variables aren't explicitly mapped to parent flow data pills, they won't be available downstream.

Variable type mismatch between subflow and parenthigh likelihood

Compare the variable types in the subflow's Output section with the data pills being passed to the parent. Check sys_flow table records for both flows to verify data types match exactly.

Subflow completing before async operations finishmedium likelihood

Check execution details in sys_flow_context table for the subflow execution. Look for steps completing out of order or async actions (like REST calls) that haven't finished before the subflow returns.

Incorrect output variable names in parent flowmedium likelihood

In the parent flow, verify the data pill names match exactly with the subflow's defined output variable names. Check the subflow's Output section for the exact spelling and case.

Subflow execution failing silentlylow likelihood

Check sys_flow_context table for error records related to the subflow execution. Also verify the subflow's error handling isn't swallowing exceptions that prevent proper output generation.

Question 2

How do you fix Flow Designer Subflow Not Passing Variables Correctly?

Accepted Answer

How to fix it Navigate to Process Automation > Flow Designer and open your parent flow. Click on the Call Subflow action that's having the variable passing issue. Click the Outputs tab in the Call Subflow action configuration. For each output variable you need in the parent flow, click Create Variable and map it to the corresponding subflow output. Verify the variable types match by opening the subflow and checking Flow Logic > Outputs section. In the parent flow's Call Subflow outputs, ensure each variable type matches exactly (String, Boolean, Integer, etc.). Check for async timing issues by opening the subflow and looking for actions like REST Step, Wait for Condition, or Script Step that might not complete before output assignment. If async actions exist, ensure the Set Flow Variables action that assigns outputs comes after these async steps in the flow sequence. Double-check variable names by comparing the subflow's output variable names (in Outputs section) with the data pill names being referenced in the parent flow. Test the fix by activating both flows and running a test execution. Monitor execution in Process Automation > Flow Designer > Executions to verify variable values are passing correctly.

Question 3

How do you prevent Flow Designer Subflow Not Passing Variables Correctly?

Accepted Answer

Always map output variables explicitly in the Call Subflow action's Outputs tab - they are never automatically available in the parent flow. Use consistent variable naming conventions between subflows and parent flows to avoid mapping errors. Design subflows to assign all output variables in a single 'Set Flow Variables' action at the very end of the flow logic. Document subflow output variable types and purposes in the subflow description to help other developers map them correctly. Create reusable subflows with well-defined input/output contracts and test them independently before using in parent flows.

Flow Designer Subflow Not Passing Variables Correctly

Symptom

Possible Causes

Debugging this in a real instance?

Solution

How to fix it

Prevention Tips

Test Your Knowledge