**Apologies for posting this a few days late. I’ve been doing some consulting work for the last several months. It has been great experience, and the extra money has been nice, but it’s meant that a lot of other things have had to be pushed to the back burner.
My posting schedule may still be a bit erratic for a while until the consulting is done, but I’ll do my best to keep it as close to the normal schedule as possible.
On to the subject at hand:
When using a branch and join construction in a ServiceNow workflow, my first instinct is to do the branch, and then do any if activities between the branch and the join.
However, this is always the wrong answer because the workflow will hang at the join as it waits for the flow to progress down the other side of the if activity.
The correct way to go about that is to do your if activity, and then run a branch off of the yes path, and another branch off of the no path.
It means that you end up having to copy a bunch of tasks so that they are on routes off of the if activity, but that way all of the routes into the relevant join reach it and flow can continue paste the point statement rather than hanging.