Unanswered

Flow creating new IcM incidents as oppoosed to updating existing active ones

(0) Share

Report

Posted on by Kona

There is a major inconvenience on how Flow handles existing IcM incidents - it creates new ones as opposed to updating existing active ones and increasing hit count when you use the "Create or update IcM incident" step.

This is the flow:

Categories:

Using flows

I have the same question (0)

All responses (4)

Answers (1)

v-alzhan-msft on at

Like (0)

Report

Hi @Kona ,

What is the name of the action "Create or ipdate an Icm incident" in your flow so we could find it in our flow and have a test on it?
Could you please share a screenshot of the "Create or ipdate an Icm incident"action in your flow?
It seems that the "Create or ipdate an Icm incident" action in your flow would always create a new one instead of update an existing one.
Have you enter the IcM incident ID in the "Create or ipdate an Icm incident" action so that the flow would check for the existing one?

Please share more details so we would try to provide a proper workaround for you.

Best regards,
Alice

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
Kona on at

Like (0)

Report

Hi Alice,
Thanks for the reply.

What is the name of the action "Create or ipdate an Icm incident" in your flow so we could find it in our flow and have a test on it?

The name of the action is "Create or update an IcM incident":

This is the screenshot (I had to hide routing and correlation IDs):

It seems that the "Create or ipdate an Icm incident" action in your flow would always create a new one instead of update an existing one.
Yes, that's correct, this is why I've started this thread 🙂

Have you enter the IcM incident ID in the "Create or ipdate an Icm incident" action so that the flow would check for the existing one?
Unfortunately, I can't use that scenario because this action would apply only to that one incident as opposed to all the new ones.

Was this reply helpful? Yes No
Kona on at

Like (0)

Report

@v-alzhan-msftHave you had a chance to look into it? Please advise, based on this we'd have to decide if we use Flow or not.

Was this reply helpful? Yes No
Verified answer

Kona on at

Like (0)

Report

We've found the root cause, it's the missing correlation ID.

Was this reply helpful? Yes No