Flow Designer - Do the following until loop in Sub Flow is not ending

[PavelP]

Hello,

I encountered an issue with Flow, I managed to get a functionality working within the loop, but when the record is closed - and the condition in the "Do following until" loop should be fulfilled - the sub-flow still sits in the "Waiting" state.

Im not sure how to troubleshoot this since the configuration is being set as expected. The only specific is its ran in subflow, but the record in the input is working with other conditions just fine.

Any suggestions?
Thanks

Pavel

[PavelP]

Hi,

if I do so, it will show its stuck on the "Wait for Condition" - which is part of the loop inside - but I'm confused - I thought if the "Do the following until" condition happens - the loop is automatically canceled.

Are you saying that if I want to close the loop, all of the conditions of the run must be completed?

Thanks

Pavel

[Voona Rohila]

Hi Pavel

Yes, inside doWhile there are wait conditions.

Once your while condition is true then steps 2-6 execute and then moves to next row

[PavelP]

Okay, in that case I have a question:

If I want to be able to close the loop, while still have the conditions inside running - would it be possible to create a parallel workflow inside the "Do the following" loop, and then Record would be closed, the Flow would be completed - even though the conditions inside are still waiting?

Thanks

[Voona Rohila]

That won't work, Steps Inside do-while should be completed to move to next row.

Can you explain your requirement,Maybe we can provide more details.

[PavelP]

Requirement is following: Within a workflow of a record, the record can be moved from "Reviewed" state to "Submit" state, in case its Returned. After move like this, if the record is updated, the state should be moved to "Pending Review" state directly (and skip the "Approval" states, that it would go through otherwise.

The return can happen multiple times - that's why the loop is being used.

We tried using a Business Rule, but it was creating conflict with flow when creating the record, so we needed to use different solution.

My desire was: using the loop to facilitate the "Return" functionality, but to break the loop the moment the Record is closed-deactivated.