Flow Designer: Service Catalog Item Error?!

[Olli_2109]

Good morning everyone,

I have an error in a service catalog item flow in the flow designer.

I copied the faulty flow from a functioning flow and only made small changes.

The RITM stage "closed complete" is not set.

The stage is not even displayed in RITM.

I have already stored the stage in the flow, as it is stored in other functioning flows. Strangely, it is marked completely yellow, see screenshot.

The last update of the record is carried out, as you can see from "completed".

It just cannot "adopt" the stage and set it in RITM.

What is the error and why is the update and the stage marked completely yellow?

Unfortunately, I have not found an answer to this anywhere.

Many thanks for an answer and best regards
Oliver

[SP22]

Hi @Olli_2109 ,
can you please check step 25 contains any record or updated any previous step record, that means flow is working as expected.

I guess yellow is to representation of flow completed.

Thanks
SP

[Olli_2109]

Hi @SP22,

thank you for your answer.

In this step I updated the Trigger RITM.  But I only set some additional comments.

I also do this in another flow and it worked fine. It 

The catalog tasks all have the "Wait" checkbox checked.

That screenshot is from working flow:

That screenshot is from error flow:

The only difference is that I create multiple sctask in the "do the following in Parallel" action.

I have an if query in the action, but according to executions it also works.

Best regards

Oliver

[Olli_2109 · Accepted solution]

Hello everyone,

The error occurred due to a "do the following in parallel" action, which created various tasks.

It is a known error that the stage cannot be set after this action.

As a workaround, create a subflow and use it to create the tasks.

This solved the problem for me.

The known error is documented here: PRB1752255

Best regards

[Dave_H]

I have encountered this issue since upgrading to Washington but can't seem to find any reference to PRB1752255. Is there any update for when this issue will be fixed?