Published Subflow Still has Draft Status

[richelle_pivec]

I have a subflow that allows me to publish it and indicates that it is published successfully. However, when I go back to the list of subflows, it is still in the Draft status (even after refreshing the browser). This does not seem to effect the Flow that calls it in Tokyo (where I created it in our Dev instance and am testing the Tokyo version). However, I need to manually move it to Rome as we will be in Rome (still) in Production when it needs to go live. When I move the Flow and the two Subflows to our Test instance (in Rome), I get an error message that basically says the subflow can't be started.

Any thoughts on how I can get the subflow to actually publish or why it says it is published and doesn't do it? Or why it works in Tokyo but not in Rome even though the Status still says "Draft" in both of them?

Thanks, Richelle

[Konstantin11]

Hi Richelle, was solving the same issue now, but in the flow.

Try to check all kinds of references (data pills), if they are valid, they may not be, even if they look as they are.

This was the problem in my case. Ended up unselecting and selecting again all catalog variables and reselecting all data pills, and it helped.

[richelle_pivec]

You are correct. That is exactly what the problem was. I found a pill in one of the subflows that had accidentally dropped the Assigned To information. Once I corrected that, the subflow indicated that it was published and (actually) published. 

Thanks, Richelle

[Konstantin11]

Cool, glad you resolved it!
You can mark the question as answered so others can find and benefit from this.
All the best, Konstantin.