Power Platform Community Forum Thread Details

Hello,

I have a PowerAutomate flow triggered manually through a button (using json formatting) in a SharePoint List (screenshot attached).

For it to work, users have to be in the Run-only users of the flow and have <edit> permission on the sharepoint list.

It works for everybody except for one single user. He has the same licences as other users.

He also is correctly in the run-only users and has edit permissions on the list.

Here is the error he encounters when clicking on "executing the flow" within the panel that opens by clicking on the list item button :

Time: "2025-02-20T14:48:45.550Z"

Session ID: c58b4c10-ef99-11ef-b337-f9a3388dc344

x-ms-client-request-id (Client->Backend Request Header): 6425ea66-be9e-4e69-9cf2-ce53206e972b

Error: The workflow 'someGUID' trigger 'For_a_selected_onboarded_employee' could not be found.

What we tried :
- clear browser cache

- connect in incognito mode

- connect on an other computer (mine)

- remove from Read-only users, and from the list permissions, and give those permissions again

- check for licences (he has the correct ones)

At this stage I don't have any other idea. He has a regular account in our company that has the same configuration as everyone else.

And this flow can be triggered by the other employees through the same buttons.

NB : a few months ago it worked for him too.

Already thanking you for hints or solutions, best regards,

Maxime J.

Categories:

Using flows

It sounds like this particular user's account is having an issue with the connection to Power Automate or SharePoint. Since you've already ruled out licensing, permissions, and browser issues, here are some deeper troubleshooting steps:

1. Check User’s Flow Permissions in Power Automate

Even though the user is in the Run-Only Users list, confirm they have access to the correct version of the flow.

Go to Power Automate → Find your flow → Click on "Edit"
Go to Manage Run-Only Users → Remove the user → Add them back.
Also, check Connections under "Data" in the Flow and ensure they are properly authenticated.

2. Ensure the Flow is Active and Not Versioning Issues

If the flow was recently updated, the user might be trying to execute an older version.

Check if there is a draft version of the flow:
- Open Power Automate and confirm if there are any unsaved changes.
- Publish any changes and test it again.

3. Verify SharePoint List Integration

Since the flow is triggered from a SharePoint list button:

Ask the user to manually refresh the SharePoint page (Ctrl + F5).
Ensure that the flow is still properly linked in the JSON button formatting.

4. Manually Trigger the Flow for the User

To see if it’s a UI issue:

Go to Power Automate
Select My Flows → Locate the flow
Click Run and choose the user’s inputs
See if the flow triggers or shows the same error.

5. Recreate the User’s Account Connection

If the user's Power Automate account is corrupted, try:

Asking the user to sign out completely from Power Automate & SharePoint.
Have them go to https://flow.microsoft.com → "Connections"
Remove any SharePoint & Power Automate connections.
Then, sign back in and retry the flow.

6. Check Admin Logs (Advanced)

If nothing works, an admin can check:

Azure AD Sign-in logs to see if there’s a blocked authentication request.
Power Platform Admin Center → "Flow Runs" for detailed logs of failed attempts.

Final Thought

Since the error states "trigger could not be found", this strongly indicates either:

The flow was updated, and the button references an older version.
The user’s authentication token is corrupted, preventing them from running the flow.
There is a Power Automate cache issue for this specific user.