Error when calling Flow from Power Apps: "Parameter 'workflowAuthorization' is not allowed"

(4) Share

Report

Posted on by VK-21070506-0

Hello everyone,

I'm encountering an issue when trying to call a Power Automate flow named "SendapprovalandfollowupviaTeams" from Power Apps.

Previously, I built a similar workflow in an old application, and it worked normally. However, after recreating it using the same method for a new application, I've found that the end-users are receiving this error.

Here is the error message the user receives:

SendapprovalandfollowupviaTeams.Run failed: {"error":{"code":"ApiHubsRequestFailed","message":"The request failed with client error: 'Input parameters are invalid. See details for more information. Details:errorCode: ParameterNotDefined. Message: Parameter 'workflowAuthorization' is not allowed on the connection since it was not defined as a connection parameter when the API was registered.'. The correlation Id is 'AZXZ21b-XXXX-XXXX-XXXX-9c85ebXZXZXXZ'."}}

Could anyone help explain the cause of this issue and suggest a possible solution?

Thank you!

Categories:

General topics

Screenshot 2025-0...

I have the same question (0)

All responses (22)

Answers (0)

yashag2255 24,769 Super User 2024 Season 1 on at

Like (0)

Report

Hi @VK-21070506-0

Can you remove the flow from the app and add it back again? (refresh the flow in the app before you add it back)

Generally, if you add an action in the flow after adding it to the app, the flow needs to be removed and added back. It is the same if you change any of the run only user settings after adding the flow to the app.

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No
VK-21070506-0 14 on at

Like (0)

Report
Thank you for the suggestions.

I have an update with more information on this issue. From further testing, I've found the problem to be very specific:

Who is affected: The issue only occurs for new users accessing the app for the first time. (Existing users do not have this problem).

Test Conditions: I created a completely new app and Flow. As the Owner, I can run the Flow without issue, but any user I share the app with immediately gets the error.

So, I'm wondering if there has been a recent update or change to the "When Power Apps calls a flow (V2)" trigger that could be affecting the permissions for shared users.

Was this reply helpful? Yes No
Eric Lee 8 on at

Like (3)

Report

Hi, I just want to share that you're not alone. I am also facing the same issue, and a few other users have reported similar problems in this thread:

Power Automate Flow Triggered from Power Apps

In our case, the flows used to work perfectly fine before, but the problem suddenly started around 18/7/2025 . I've tested many different ways to fix it (including recreating flows, sharing ownership, using test apps, etc.), but nothing works. So I’m quite sure this is not a user-side issue, but something wrong on Microsoft’s side.

Now we’re just hoping Microsoft will detect this and provide a fix soon.

Was this reply helpful? Yes No
Suggested answer

Power Platform 1919 1,890 on at

Like (0)

Report

Hi @VK-21070506-0,
Can you please also add a screenshot of how you are calling the flow like Button's OnSelect Property pic?
based on that we can comment on the same?

if you still facing the issue, try creating a copy of the flow and attach it to the app and see if it works?

Please give the mentioned solution a try and let me know whether it works for you.
If it solves your issue, feel free to mark this thread as answered.
Please make sure to like the response!
Thanks!
- Hemanth Sai

Was this reply helpful? Yes No
stampcoin 5,058 Super User 2025 Season 2 on at

Like (1)

Report

@CU21070321-0, @VK-21070506-0

Sounds like some update caused, Please send ticket to the product support.

Here is the link: https://admin.powerplatform.microsoft.com/support/requests

1 people found this reply helpful.

Was this reply helpful? Yes No
Stefan_Gi 42 on at

Like (1)

Report

We have exactly the same problem with one of our PowerApp (V2)-triggered flows since today. Interestingly, other V2-flows still work as expected, but one particular flow stopped working today and does not get triggered by the PowerApp. The owner can trigger it, but other users can't. Instead, the following error message appears for them:

"AddTicketAttachment.Run" failed: {"error":{"code":"ApiHubsRequestFailed","message":"The request failed with client error: „Input parameters are invalid. See details for more information. Details:errorCode: ParameterNotDefined. Message: Parameter 'workflowAuthorization' is not allowed on the connection since it was not defined as a connection parameter when the API was registered.“

I also recreated the flow and added the new one to the PowerApp, but no success. The error message above appears again.

Definitely looks like a problem due to an update in Power Automate backend that was rolled out during the weekend, because the flow worked flawlessly for 1,5 years.

Was this reply helpful? Yes No
AlanWells 6 on at

Like (1)

Report

Same issue with me, just started occuring today for apps that have been in use for 6+ months.

I have deleted and recreated the flow within the app, works for the account I use to create the apps but not for anyone else.

Was this reply helpful? Yes No
SL-17100357-0 14 on at

Like (1)

Report

We have encountered the same issue as well with the following error:
TestFlowWithError_18Jul.Run failed: {"error":{"code":"ApiHubsRequestFailed","message":"The request failed with client error: 'Input parameters are invalid. See details for more information. Details:errorCode: ParameterNotDefined. Message: Parameter 'workflowAuthorization' is not allowed on the connection since it was not defined as a connection parameter when the API was registered.'.

Seems all new created flows after last friday got the same error. We tried duplicating (using "Save As") an old flow (that was working before with exact same connections), and added the flow into the same solution and connected it to Power Apps, the flow then gets the same error above.

One quick solution that we found is: share the app access to the user as "Co-Owner" the flow worked smoothly with no more error. Anyone knows if there is any better solution?

Was this reply helpful? Yes No
Suggested answer

Shinnara7 36 on at

Like (1)

Report

I'm facing same issue as well. Hope following steps will fix your issue.

~ Check your flow run only user setting. set provide by run only user to flow owner connection.

~ Remove your flow from power apps and readd. Then publish.

~ Make sure user are using updated version of your apps.

These step solve issue for me. Good Luck guys

Was this reply helpful? Yes No
TomVD_VDP 19 on at

Like (4)

Report

Same problem here: Power App calling Power Automate flows, since this morning (but yesterday was a bank holiday, so possibly the problem is already a few days old) results in the error described above. It does seem to happen only for users that are 'new' to the Power App application.

The solution suggested by Shinnara7 is no option for me, since I do not want to set the connections used in the flow as 'provided by run-only user' (instead I wish to use a specific predefined connection (with dedicated credentials)).

The problem is known as issue number 5343606: https://admin.powerplatform.microsoft.com/support/knownissues/5343606

Was this reply helpful? Yes No