You are viewing limited content. For full access, please sign in.

Question

Question

All steps completed but shows as In Progress

asked on February 19

I have a process diagram too complicated to post here since it would be too hard to read with how many activities are on it, but the gist is:

 

Initial submission goes to parallel gateway

Parallel gateway splits into 4 paths, each with an inclusive gateway

Each inclusive gateway has its own branching paths that may or may not be met, but at least 1 will always be met

Inclusive gateway paths end at another inclusive gateway, since we don't need to wait for all paths (not all will be active)

All 4 "closing" inclusive gateways go to a parallel gateway to close, then the process finishes

 

This works as expected in the sense that when all 4 parallel gateway paths are done the process completes, but the process still shows as "In Progress" even though there are no steps left to complete. Am I using gateways wrong?

0 0

Answer

SELECTED ANSWER
replied on February 22

Hi Jared,

I actually figured it out myself. At each review step, if the reviewer rejected, it interrupted any incomplete reviews for that group and looped back to start over. If that happened, the rejected task and any interrupted tasks would never hit the "close" inclusive gateway.

I changed the flow so all of the steps route to the "close" inclusive gateway whether they are approved, rejected, or interrupted, and then after that used an exclusive gateway to loop back (if the last user action was a rejection) or move forward to the closing parallel gateway to mark this group complete.

After repeating the steps that caused my issue, this time it completed successfully.

1 0

Replies

replied on February 19

Are there any in-progress tasks/steps listed in the Monitor page? 

0 0
replied on February 19

No, every single step is marked as Completed and the End Event for the end of the process completed.

0 0
replied on February 22

Open up a support case so we can take a look. If you select the instance, you could try to click retry if that action is available. Otherwise, we can likely provide a script to fix the instances and troubleshoot why it happened. 

0 0
SELECTED ANSWER
replied on February 22

Hi Jared,

I actually figured it out myself. At each review step, if the reviewer rejected, it interrupted any incomplete reviews for that group and looped back to start over. If that happened, the rejected task and any interrupted tasks would never hit the "close" inclusive gateway.

I changed the flow so all of the steps route to the "close" inclusive gateway whether they are approved, rejected, or interrupted, and then after that used an exclusive gateway to loop back (if the last user action was a rejection) or move forward to the closing parallel gateway to mark this group complete.

After repeating the steps that caused my issue, this time it completed successfully.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.