When working with ControlUp’s flow automation, users may encounter a situation where updating the input variables of a subflow does not immediately reflect those changes in the parent flow’s Run sub flow node. This occurs because the Run sub flow node loads the subflow’s input variables only once per parent flow page load. Consequently, if you modify the subflow inputs but remain on the same browser tab with the parent flow loaded, the Run sub flow node can continue to display the previous set of inputs, giving the appearance that the updates have not applied.
This behavior is by design and there is no dedicated “refresh” button to update the inputs dynamically within the same session. However, it is not necessary to remove and re-add the subflow node to refresh the inputs. The recommended procedure to see the updated input variables in the parent flow is to first save the changes made to the subflow, then perform a browser page refresh (such as pressing F5) on the parent flow’s tab. After the page reloads, opening the Run sub flow node will reveal the updated input fields. Existing input values will be preserved through this process, allowing the user to simply add values for any new inputs before saving the parent flow.
It is important to note that if any new input variables introduced in the subflow are not filled in within the parent flow’s Run sub flow node, those inputs will have empty values when the subflow executes. Therefore, users should ensure that all necessary new inputs are populated to avoid unintended empty values during runtime. This behavior is consistent across current ControlUp flow environments and is not indicative of an error but rather a reflection of how input variables are cached per browser session for performance reasons.
For further details on managing flows and subflows in ControlUp, users can consult the ControlUp documentation at https://docs.controlup.com, which provides comprehensive guidance on flow design and best practices. This approach ensures users can effectively manage input variable updates without unnecessary node removal, streamlining the development and maintenance of complex automated workflows.
Read the entire ‘How to Refresh Updated Subflow Input Variables in ControlUp Flows Without Re-adding the Node’ thread below:
When adjusting the input variables of a flow that is used as a subflow, you have to remove and re-add the subflow to the main flow for the updated input fields to appear. Is this expected behavior, or am I missing a refresh button?
Hi Brecht! Good question. As far as I can tell there isn’t a dedicated refresh button, but you shouldn’t need to remove and re-add the sub flow either.
My understanding is that the Run sub flow node picks up the sub flow’s input variables when the parent flow loads, but only once per page load. So if you edit the sub flow and then head back to the parent in the same tab, it can keep showing the old list.
Could you try this and see if it does the trick?
• Save your changes to the sub flow
• Refresh the browser page (F5) on the parent flow
• Open the Run sub flow node. The new inputs should be there, with your existing values kept
• Fill in any new ones and save the parent flow
Worth keeping in mind: any new input that isn’t filled in on the parent won’t get a value when the sub flow runs.
Let us know how it goes!
Hi Brecht,
There’s no refresh button, and you don’t need to remove and re-add the sub flow. The Run sub flow node only reads the sub flow’s inputs when the parent flow loads, so after editing the sub flow it can keep showing the old list.
To fix it:
• Save your changes to the sub flow
• Refresh the browser page (F5) on the parent flow
• Open the Run sub flow node and fill in any new inputs (existing values are kept)
• Save the parent flow
A new input that isn’t filled in on the parent gets an empty value when the sub flow runs.
Let us know how it goes!
Continue reading and comment on the thread ‘How to Refresh Updated Subflow Input Variables in ControlUp Flows Without Re-adding the Node’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers, ControlUp Workflows
