on selected message see error "Workflow did not complete its run"

[BruceWang_01]

on selected message see error "Workflow did not complete its run"

Today, when i try to open some of my flow the one tiger with "on selected message", some of them show "on selected message see error "Workflow did not complete its run" directly.

But not pop the adaptive Card

[BruceWang_01]

Add the error page

[BruceWang_01]

Any advice or comments, please kindly let me know. thanks.

This error seems new , and haven not found enough reference docs.

[mmathieu1987]

This error is also affecting me today. Agreed appears to be new. 

[sbrothers123]

Hello,

Looks like if you remove any "Compose" actions from within the flow in question, the issue is resolved.

[BruceWang_01]

Yes, the solution have provided in my another topic for the same issue.

But, back to issue i think Microsoft need fix the issue instead we remove compose.

Because, compose is existing in my most of flows...the change take much efforts and add risk to steady flow

[BruceWang_01]

@Heddanewman  @Ashley_italent @heaher_italent  @Carly_iTalent  Hi All, is there anyone can help and follow the error caused By Microsoft.

As above discussions - recently, our own Flow suddenly cannot use, based on friends research, remove "compose" is able to avoid issue.

But this will cause much re-work. So we want the community would be able to review and advice and locate the issue if possible.

Honesty, this error influence us...we not able to run our own flow and it already block our daily work.

Thanks for any comments and advices.

[heaher_italent]

@BruceWang_01  - Thank you for the @mention. Let us look into this and see what we can help with.

Looping in @Jim_iTalent  as he is your Community Manager, @AnnaChu is your Community Program Manager here in Power Automate.

Best,

Heather

[AnnaChu]

Hi @BruceWang_01 There's a fix that's currently rolling out for it. In the interim we've found the reason for the error is usually the presence of the compose action in the flow. So if it's possible to remove that within the flow that is one way to get around the error. Hope this helps.

[BruceWang_01]

@Ann  Thanks for the feedback, once the fix push to production please kindly let me know, thanks.

I have much flow be influenced, I would wait for the official fix.

By the way,  I would advise team consider this as a serious issue. Because the issue block much flow the one daily run. Thanks

Except that, try to confirm with you which is the general flow to raise production issue, thanks for any advices.

PS. Except this community, I have not seen another ways to follow and raise production issue. But actually, community cannot get immediately response or feedback.

[BruceWang_01]

@heaher_italent  Thanks for the feedback and transfer

[FraserMagee]

Is there any way we can get an update on this?  We too are impacted by this bug

[BruceWang_01]

Fraser Magee,

Today i check the flow, the error have disappeared. You can try your side, too

[BruceWang_01 · Accepted solution]

4/18/2022 - Today i check the flow, the error have disappeared.

[FraserMagee]

unfortunetly - I'm still getting the error on my side.
I am the flow owner/creator.  I have it shared to a Power Automate 'service account' and it is running on with per user perms.  No changes were made on our side - it has been working for almost 2 years without issue..... until recently.  The workflow completes successfully for everyone in the org except for me.

I'm finding the "error details" link slightly useless as it just launches Teams and takes me to power automate (teams) -- there are no details to be found. 😕 ugh

[AnnaChu]

Hi @FraserMagee thanks for flagging. I've messaged folks on the Power Automate team to take a look at this issue and I'll get back to you as soon as I hear back.