Flow breaks when the state of catalog tasks are manually changed

[sjjantz]

I have a flow attached to a Catalog Item which basically flows as noted below. If any of the tasks are manually changed to anything other than "closed complete", it breaks the flow, the fulfillers of this request need the ability to track the state of each task. I need to know how to modify this flow so that it will recognize when the first three catalog tasks all change to "closed complete" so the next approval request can be created.

Trigger: Service catalog

Actions

Get Variables from Catalog Item

Do the following in Parallel

-Ask for manager approval on Requested Item

-Create Catalog Task

-Create Catalog Task

-Create Catalog Task

If condition - If catalog tasks are complete

then - Ask for approval on Requested Item (different manager)

If condition - if both approvals are approved

Then - Create Catalog Task

If condition - if catalog task is complete

then  - Update RITM/Request Item Records

[VaishnaviK3009 · Accepted solution]

Hi @sjjantz ,

I’ve attached my Flow Designer screenshot,please check !!

Mark this as Helpful if it clarifies the issue.
Accept the solution if this answers your question.

Regards,
Vaishnavi
Technical Consultant

[sjjantz]

Hello Vaishnavi,

Thank you for your very helpful response. This mostly worked, only it is waiting for the first approval to be approved before creating the second approval, whereas we do want the first approval to be requested up front, however it is not required until prior to the deployment task and we do not want the second approval being requested until the request is ready for deployment. I can't seem to figure out which step is preventing that from taking place. 

[VaishnaviK3009]

Hi @sjjantz ,

Glad it helped! The new behavior you’re seeing is due to the “Ask for Approval” step for the first approval.

“Ask for Approval” will pause the flow until it is approved, which is why the second approval is not being created when expected.

To fix this:

• Replace the first approval with “Create Approval” (so it’s requested upfront but does not block the flow)

• Keep the second approval as “Ask for Approval” at the deployment stage

This way, the flow won’t wait on the first approval and will only pause when the second approval is triggered.

Mark this as Helpful if it clarifies the issue.
Accept the solution if this answers your question.

Regards,
Vaishnavi
Technical Consultant

[VaishnaviK3009]

Do this create approval !

Mark this as Helpful if it clarifies the issue.
Accept the solution if this answers your question.

Regards,
Vaishnavi
Technical Consultant