Using a Go Back To Step inside a Parallel Branch in Workflow Studio

jarsharr26
Tera Contributor

Friday

I am working on a Flow that involves waiting until the Start Date of a Change Request. I was wanting to add in something to the Flow that restarts the wait if the Start Date changes. My current implementation has no parallel branches; it is set up to repeatedly wait a set amount of time and check if the start date has changed and restart the process if it has. Otherwise, it will keep looping until the start time arrives and takes further action.

 

I was wanting to know if its possible to set up a similar idea by using a 'Do the Following in Parallel' block, where one branch is a 'Wait for Condition' to see if the Start Time Changes and another branch that does the waiting until the start time. In the Wait for Condition branch, it would have a go back to step to before the parallel block even begins, and the other branch would complete all additional actions and end the flow. 

 

Is such a set up possible? Or is my current implementation without the parallel block going to be the only way to do what I want? 

 

Thanks,

Jarrod

0 Helpfuls
  • 253 Views
1 REPLY 1

G Ponsekar
Mega Guru

Sunday

Hi @jarsharr26 ,

 

Your current implementation, without parallel branches, is the most robust and supportable way to achieve your goal of waiting and checking for changes repeatedly.
 
Your current design with a loop that checks the Start Date and repeatedly waits is the standard, reliable method for this scenario in Flow Designer. It ensures that the flow is constantly aware of the current Start Date.
To optimize your current flow and make it more efficient, consider these improvements:
  • Variable for the original start date: Store the original Start Date in a flow variable at the beginning of the process. In your loop, check if the Start Date on the record has changed by comparing it to the value in your flow variable.
  • Use Wait For A Duration Of Time: This is more efficient than checking repeatedly with short timers. For example, you can set the flow to wait 15 minutes and then re-evaluate the condition. This reduces the number of operations and system load. 
Your existing implementation is the correct and reliable way to handle this dynamic "wait and re-evaluate" behavior. The parallel branch approach, while a creative idea, is not a valid construct in Flow Designer for this type of loop
 

If I could help you with your Query then, please hit the Thumb Icon and mark as Correct !!

 

Thanks, GP

0 Helpfuls