Join in Workflow not progressing even though all tasks above are complete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2015 09:58 AM
Hello,
I've just run into an issue while updating a workflow. In this workflow I just wanted to place a branch, then have 2 tasks created, then use join to make sure both tasks are completed before moving on in the workflow. It's a very simple setup that I have in several workflows. It usually works perfectly. So I created a branch, the two new tasks, and the join. I placed them in the proper place in the workflow and made sure all transitions were correct. When testing I've found that even though both tasks are completed, the join is not completed so the workflow never moves on. I've tried deleting them all and starting over and it still doesn't work. If I take out the branch/join and just create the tasks inline, it works just fine so I don't think there is a problem with the tasks. What's weird is I have this EXACT setup working great earlier in the workflow. The new tasks when closed are returning '3', just like the ones above that work. I don't think I've created a branch/join since we upgraded to Eureka so I was wondering if anyone else has run into this? I've inserted a screenshot of the workflow (it's pretty basic I think) and below that a shot of the workflow 'stuck'.
and then after it runs:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-15-2015 02:03 PM
Did you ever get this working? I just built a new workflow branch similar to your setup, and it worked fine (on Eureka Patch 7).
I would have asked that you verify exactly what activity results the "Complete" and "Incomplete" conditions are looking for, but it looks like your Join activity isn't even completing to generate a result (since it's still green).
As far as I know, there's no way for us to force Join activities to "complete." The Script contained in the actual Join Workflow Activity Definition may have more information: https://[instance].service-now.com/nav_to.do?uri=wf_activity_definition.do?sys_id=7c9a2ba9c0a8016500...
I didn't spend a lot of time digging into that code, but it looks like having other Join activities and/or other incomplete activities in the workflow may have an impact on when this particular Join activity completes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-15-2015 02:51 PM
We use Branch and Join in many workflows. It works fine in Eureka.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-15-2015 03:07 PM
Check the following thread. It might be useful:
Re: Point/Benefit/Impact of Branch Activity in Workflows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-08-2024 03:11 PM
@saritha9 Broken Link?