Why is a particular Flow not setting the RITM's Stage to Completed (but another Flow is)

GoBucks
Mega Sage

We have 2 Flows-- Flow A and Flow B-- that have service catalog triggers for 2 different service catalog items.

 

Flow A creates a single catalog task. After the catalog task is completed, and the Flow verifies that there are no other manually created tasks under the parent RITM, the parent RITM's Stage is set to Completed.  This one is working as expected.

 

Flow B is only slightly more complex.  Flow B creates 4 parallel paths, using the "Do the following in Parallel" flow logic, with 2 catalog tasks created serially, in each parallel path.  After all 8 catalog tasks are completed, and the Flow verifies that there are no other manually created tasks under the parent RITM, the Flow is configured to set the parent RITM's Stage is to Completed-- just like in Flow A.  However, upon Flow B's completion, while the RITM does get set to active=false, the RITM's Stage remains set to 'work in progress' and NOT Completed.  Why is this the case?

 

BOTH Flow A AND Flow B have the same Stage definitions and the Completed Stage is placed in the same location in BOTH Flows-- right after the catalog tasks, prior to the final action which simply sets the RITM state to Closed Complete.  So, why is Flow B NOT setting the RITM's Stage to Completed like Flow A does?

 

Stage definition for BOTH Flows:

GoBucks_0-1717607549288.png

Again, the above is just fine with Flow A.  Flow B, as described above, never moves the RITM to a Stage of Completed.

5 REPLIES 5

@Adithya MThe Problem has been confirmed and is currently in a state of Testing.  There is no confirmation yet on what future release(s) this will be fixed in though.