Scoped app subflow error activating after assigned to flow

[Wm Hadley]

I have a scoped app that is causing problems when assigning a subflow to a flow. I cannot recreate the behavior from global, and it is consistent across 3 tenants. The details are as follows:

• Version is Vancouver build date 11-09-2023_1854
• Subflow saves and publishes when not assigned to flow
• Subflow "publish" option changes to "activate" option when assigned to flow
  • It also changes its label from Subflow to Flow in the Flow Designer tab (see attached image)
• Subflow cannot activate and errors after assigned to flow and "activate" button appears
  • It is failing because subflows open a modal showing impacted flows, but that does not open because it is being treated as a flow
• Subflow maintains properties of subflow and can be selected as a subflow from a flow
  • Flow will error when trying to save and shows a blank space where the subflow would be in the actions window (see attached image)

The subflow becomes completely unusable, and I am completely blocked on dev work that I need to complete. I don't know why this is happening. I've tried different browsers, and the only thing that seems to change the behavior is whether I am in a scoped app or Global. I previously opened a ticket with SN, and they said it was because I am using version control in the scoped app and that everything had to be committed or else it was stuck in a checked out state. I can confirm that is not the case. I have committed all the flows and subflows and the same behavior persists.

Has anyone else seen this type of issue?

[Amit Verma]

Hi @Wm Hadley 

Please try the below troubleshooting steps :

1. The sub-flow created is not having any action steps. It has inputs, outputs and flow logic only. For Sub-flow to be available for testing and publish it should at least have one action step.

2. Please go through each step of your Sub-flow / Flow and check all Data Pill References to ensure that they still exist in the Data Pane of the Flow Designer. If the Data Pill Reference is no longer visible from the Data Pane then it is likely outdated and needs to be removed from being used in your actions.

You must then ensure that all outdated Data Pill References have been deleted / replaced with existing ones.

Thanks & Regards

Amit Verma

[Wm Hadley]

All steps mentioned have either been tested or are not relevant to this case. This is a bug, which I will be updating the post to indicate. Thank you!

[Wm Hadley · Accepted solution]

After working with SN support, this is a known bug that is planned to be fixed with the Washington DC release. The workaround is to open Flow Designer from Self Service and not from Studio. When opening from Self Service, the sub flow is editable and can be published as expected.