cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JRKBMM
New Member

permissions to perform action 'run' on scope '/triggers/manual/paths/

Hello everyone

 

I used until now the power automate api to retrieve data from a workflow on the qualtrics solution. and it worked great!

 

But since a few days, all my flows are in error. However, I haven't changed anything, neither on Qualtrics nor on PA.

 

here is the error message i get :

 

{  "message": "{\"error\":{\"code\":\"AuthorizationFailed\",\"message\":\"You do not have permissions to perform action 'run' on scope '/triggers/manual/paths/'. Verify you are making the request with the appropriate HTTP method. See http://aka.ms/logic-trigger for details.\"}}", "needRetry": false }

 

I don't understand, I have set on Qualtrics that this POST API does not require any authentication ? What could have changed in your opinion? The peculiar thing is that when I make a test call on the API it works perfectly, it's in the global workflow that I get the failure.

 

Thanks for your help 🙂

4 REPLIES 4
KoenJanssensPD
Post Patron
Post Patron

@JRKBMM did you ever found a solution? I have a flow with a trigger "When a HTTP response is received" that gives the same error when the POST URL is being called by a third party. However, when I call the same POST URL from postman it works fine...

KoenJanssensPD
Post Patron
Post Patron

@JRKBMM , I just stumbled upon this comment on stackoverflow: https://stackoverflow.com/a/66294880/1381490

It states that the "sp" parameters should be changed from "sp=%2Ftriggers%2Fmanual%2Frun" to "sp=/triggers/manual/run"... I tried that and my flow got triggered again!

@KoenJanssensPD   Thank you so much for this response.  I've had a ticket open with Microsoft on this for more than 2 weeks.  Would have never guessed that the encoding of the / would be the issue.  Not sure if the power automate app should be encoding the URL for post commands.   -Todd

rkrull1956
Regular Visitor

Had this same issue with sp = %2Ftriggers%2Fmanual%2Frun changed to sp = /triggers/manual/run ... issue was resolved (Flow executed properly).

Helpful resources

Announcements
Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Community Calls Conversations

Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Top Kudoed Authors
Users online (6,710)