Microsoft Teams Workflows / Power Automate "For a selected message" flows fail to launch for non-owner users.

Question

Microsoft Teams Workflows / Power Automate "For a selected message" flows fail to launch for non-owner users.

Petrus Azevedo 25

Issue:

Error:

SimpleRunner: Something went wrong, please try again.

Missing trigger URL / Missing trigger URI.

This workflow can't be run from here.

Impact:

Multiple users impacted after a recent Microsoft Teams update.

Validation Completed:

Production flow works for the owner.
Brand-new test flow fails with identical error.
Reproduced on Teams Desktop AND Teams Web.
Refreshed trigger connections.
Removed and re-added run-only users.
Saved and re-enabled flow.
Cleared Teams cache.
Reinstalled Teams.
Logged out/in multiple times.
Confirmed Workflows/Power Automate app association.

Assessment:

Not a client, cache, profile, flow, or connection issue.

Teams Web failing eliminates desktop client cause.

Root cause appears to be Microsoft Teams Workflows service-side failure to resolve the selected-message trigger URI for non-owner users.

0 comments

7 answers

Your answer

Answer 1

We are experiencing the same issue... we have done all of the above. In our case, more than 50 users were affected and most of them were able to get it working by resetting MS Teams

from the computer:
Settings → Apps → Installed apps → Microsoft Teams → Advanced options → Reset

but we still have 10+ users with the issue after all that troubleshooting.

these are the troubleshooting steps I have done..

Reset MS Teams thru Settings
Remove Power Automate connection
Remove all cached credentials from Crendential Manager (both Web and Windows)
Update the flow trigger to use see if it would create a different URI
Clear MS Teams Cache (with both using a company tool and manually deleting everything in %userprofile%\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams)
Multiple restarts
add user as co-owner (this works but the flow uses my connection, not the use-only user)

Answer 2

Michelle-N 20,645 Microsoft External Staff Moderator

Hi @Petrus Azevedo
Based on the validation completed, this does not appear to be a client-side, cache, profile, connection, or individual flow configuration issue.

The key points are:

The production flow still works for the owner.
A brand-new test flow fails with the same error for non-owner users.
The issue reproduces in both Teams Desktop and Teams Web.
Trigger connections were refreshed.
Run-only users were removed and re-added.
The flow was saved and re-enabled.
Teams cache was cleared and Teams was reinstalled.
Users signed out and back in multiple times.
The Workflows / Power Automate app association was confirmed.

Because Teams Web is also affected, this rules out a desktop client-only issue. Because a newly created test flow fails the same way, this also makes a corrupted existing flow unlikely.

The error messages “Missing trigger URL / Missing trigger URI” and “This workflow can't be run from here” suggest that Teams is failing to resolve the selected-message trigger URI for shared or non-owner execution.

At this point, I would recommend opening a Microsoft admin support ticket and including the repro details, affected users, timestamps, flow IDs, environment ID, Teams client version, browser test result, and screenshots/HAR logs from Teams Web.

Thank you for your patience.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Randy Kelly 0 Reputation points

2026-07-17T14:27:58.6+00:00

We are seeing what could be the same error. The same message is displaying for some not all run only users when they try to execute the flow from the compose box.
Petrus Azevedo 25 Reputation points

2026-07-19T08:10:52.3833333+00:00

Thank you
Petrus Azevedo 25 Reputation points

2026-07-19T08:13:51.8433333+00:00

As a workaround, I have added the users as co-owners of the process-critical flows.
Michelle-N 20,645 Reputation points Microsoft External Staff Moderator

2026-07-20T13:29:56.2933333+00:00

Hi @Petrus Azevedo

Thank you for sharing your workaround. Please let me know if you need anything else.
Michelle-N 20,645 Reputation points Microsoft External Staff Moderator

2026-07-21T14:08:32.8433333+00:00

Hi @Randy Kelly

Thank you for sharing your issue.

Since this appears to be a different scenario, I recommend creating a new thread and including details. This will help avoid mixing multiple issues in one discussion and allow moderators to focus on your specific case more effectively.

Creating a separate thread will also enable us to request additional information via private message if needed, while helping protect personal or organizational data.

Thank you for your understanding.

Answer 3

Tatyana Ryskina 5

Hi @Michelle-N , we are experiencing exactly the same issue, and the only thing that helps is granting a "co-owner" permission to the run-only users, which is not an ideal workaround. Could you please confirm this issue is already registered by Microsoft team as a defect, and what else can you advise in the meantime?
(we tried everything Petrus Azevedo mentioned above but find it risky to let every user becoming a co-owner)

Michelle-N 20,645 Reputation points Microsoft External Staff Moderator

2026-07-23T13:08:26.79+00:00

Hi @Tatyana Ryskina

Thank you for sharing your issue.

Since this appears to be a different scenario, I recommend creating a new thread and including details. This will help avoid mixing multiple issues in one discussion and allow moderators to focus on your specific case more effectively.

Creating a separate thread will also enable us to request additional information via private message if needed, while helping protect personal or organizational data.

Thank you for your understanding.
Tatyana Ryskina 5 Reputation points

2026-07-29T08:16:40.9333333+00:00

Hi @Michelle-N , We believe this is just the same issue as the topic starter described and other users confirm here in the thread.
Do you have any updates on this please? Have this been logged as a defect? I've reported a bug via Teams option, but cannot see any details whether it was accepted or not.
The issue is still in place for us, but we are not OK to either grant run-only users more permissions or degrading the MS Teams version.
Can you help please?
Randy Vogl 5 Reputation points

2026-07-29T13:49:54.08+00:00

@Tatyana Ryskina I would agree this is the same issue. I have the exact same symptoms as the original comment and the suggested work around has gotten select users back up and going but they have to be co-owners this seems to have been caused by a Microsoft teams update that rolled and started displaying the run history from the best I can understand. I still have a case outstanding, one user recommended rolling back the teams version. This workaround didn't work for me. I have having this issue on the desktop and web version.

Answer 4

Mohamed Gachita 0

the same issue as above , any solution ? or how to get support on this ?

Randy Vogl 5 Reputation points

2026-07-22T23:05:59.7266667+00:00

I have submitted a power automate support ticket. So far there haven't been any troubleshooting steps beyond what are listed here. the only workaround is the co-owner option but that has major drawbacks.
Mohamed Gachita 0 Reputation points

2026-07-28T06:39:32.4866667+00:00

Hi, did you got any fix or update in your support ticket ?
Randy Vogl 5 Reputation points

2026-07-28T07:25:01.5433333+00:00

No, supposedly they are still working on it. Right now we are still forced to use some of the other work arounds suggested by others. The case has been transferred to like 4 teams and no real action taken.

Answer 5

Randy Vogl 5

@Petrus Azevedo did you find a resolution to this issue? I have the exact same issue. It works for the owner but no one else.

Pravin Gumgaonkar 0 Reputation points

2026-07-23T14:36:03.1233333+00:00

@Petrus Azevedo did you find a resolution to this issue? I have the exact same issue. It works for the owner but no one else. I am facing the same issue, Create the workflow multiple times but no use.
Subba Reddi Tummuru (WIPRO LIMITED) 6 Reputation points Microsoft External Staff

2026-07-30T19:13:29.4966667+00:00

It seems this is a bug at Microsoft side, and the fix is rolled out. Please check now, it is working.