"Workflow did not complete its run" - When select the action through "on selected message"

[BruceWang_01]

Summary - "Workflow did not complete its run" - When select the action through "on selected message"

Condition - Today suddenly face this issue, the same actions are able to use and not issue.

Other Users - For same action, other user donot have this issue, so guess my id issue. But i have tried to delete/turn off recent create or failed flow. The issue still existing.

Other Action - Not all actions facing this error, but some.

Checking done - 

1. Remove new create flow  -- not fix the issue

2. Copy failed flow  -- new flow also have this issue

3. Switch platform like use Daas instead PC -- still have this issue

4. Check Other Actions - Some actions have this issue but some not. 

     Have issue actions, everytime have this error when i try to open

     Donot have this issue actions, everytime donot have this error when i try to open

Snapshot - 

[Richard-C]

Currently facing the same issue.

Question for you @BruceWang_01 Are you the one that created the flow for your team and are you the only one for whom it is failing?

In my team, I seem to be the only one that lost access to it. I am the one that created the flow. I tried adding another user as Owner and test if he still had access and he does, so it doesn't seem like it would be linked to the owner...

[BruceWang_01]

Hi Richard,

Yes, same with you 

I am the owner of the flow and i am the only one cannot user this flow.

Other run only users, have not face this issue.

PS. Other flow creator in my company face the same - Owner cannot run some flow, and run only user not be influenced.

So...back to question ~ it is not caused by Company Policy but caused by Microsoft! 

Hope we are not come from same company, key word 'SS'

[LukeAHartley]

I have this exact problem too and it started a few days ago.  As an interim solution I have had to create duplicate flows and adjust the trigger to a manual one.  However one of my flows makes use of information in the message I trigger it from so thats not easy (or worth my time) to do as a manual trigger.

This really needs to be looked in to a fixed as its causing quite a lot of issues and additional work.

[BruceWang_01]

Yes. So summary all feedback in this channel... this issue should be caused by Power Automate this platform.

Now sure how can we raise the priority and let the Power Automate Developer know

[90Arrow90]

We have the same issue. I can run it when i remove all Compose Actions. IF i add a Compose Action then it failed again.

[KrithikaS]

@90Arrow90 I can confirm that when I remove compose actions, the flow does get triggered. 

[LukeAHartley]

Interesting!  So has anyone tried replacing their compose actions with say a variable action so complete the same thing?

[Cri88]

Same problem here. 

@90Arrow90 solution "fixed" the issue. Thank you.

[BruceWang_01]

Hi ,

But i think this is not the solution to fix the issue but avoid the issue.

Actually, the same flow always work fine before, Until recent days.

So i think we still need Microsoft be able to locate the issue and fix accordingly.

So that all of us - no need so much re-work

[BruceWang_01]

What's  wrong with Microsoft  ???

[KrithikaS]

Agreed. This seems to have been a bug that they introduced recently.

[ejustinformacio]

Same issue here. Are there any updates regarding this?

[BruceWang_01]

Still have not seen any feedback from Official members.

But based on the feedback from other friends, remove compose will avoid this issue.

If your flow remove compose donot take much effort, you can try

[mr_mac]

Same issue here. I removed the one of the owners and it started working for him right away as a run-only user.

It is not feasible for me to remove compose functions so I could not test this option.

Hoping for a quick fix please MS.

[BruceWang_01]

Today i try the same flow -- issue disappeared, you can try the same

[BruceWang_01 · Accepted solution]

Glad to see that - the issue disappeared for my flow. You can try the same