You’re offline. This is a read only version of the page.
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 🙂
Not surprised you had no luck with MS Support. I have had tickets open for over 6 weeks and we eventually closed them with no solution because the support team didn't have a clue and instead of admitting it they just used delay tactics by asking for information that had already been supplied. You will always get the best solutions from the developer community, not Microsoft's outsourced support team.
Brilliant! Saved me a well, over 2 years after your post.
Had this same issue with sp = %2Ftriggers%2Fmanual%2Frun changed to sp = /triggers/manual/run ... issue was resolved (Flow executed properly).
@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
@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!
@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...
#1
Michael E. Gernaey
6
Super User 2025 Season 1
#2
KT-07051015-0
4
#3
GI-06050833-0
2
Share
Report
All responses (
Answers (