Power Automate Flow Triggered from Power Apps

(4) Share

Report

Posted on by SS-18070931-0

Problem:

I am using Power Apps to trigger a Power Automate flow, but I am facing an issue where the flow works fine when triggered by users in my department, but users from other departments receive an error. The error message appears on the Power Apps side, but there are no errors visible in Power Automate, and the submissions are not even appearing in the Power Automate system.

The error message is as follows:

"Submit&ApprovalFlow.Run failed: {"error":{"code":"ApiHubsRequest Failed","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 'baecf4c3-635a-460f-8226-af8c17e1e00a'.","details":[{"code":"MultipleErrorsOccurred","message..."

Categories:

General topics

image (2).png

I have the same question (0)

All responses (18)

Answers (0)

Power Platform 1919 1,890 on at

Like (1)

Report

Hi @ SS-18070931-0,
can you please share some screenshots of the flow trigger inputs and how you are calling the flow from power apps
?
so that we can analyze and propose a solution

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

Like (0)

Report

@SS-18070931-0 Hi,

You might need to double check the flow connection reference. at least the error says that.

make sure it only refers the same one.

Was this reply helpful? Yes No
EL-29011114-0 15 on at

Like (1)

Report

Hello,

I have the same error.

The apps and the flow run perfectly well when triggered by the owner of the app and flow. Then i shared, the app and the flow to a new user, execution only. And this error occurs when triggering the flow : here the full error :

{\"error\":{\"code\":\"ApiHubsRequestFailed\",\"message\":\"La demande a échoué avec l’erreur du client : « 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. ». L’ID de corrélation est « 8ceb6b1f-686c-4882-8238-f85afaad4eb3 ».\",\"details\":[{\"code\":\"MultipleErrorsOccurred\",\"message\":\"Plusieurs erreurs se sont produites. Consultez les détails.\",\"details\":[{\"code\":\"BadRequest\",\"message\":\"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.\"}]},{\"code\":\"FullNonLocalizedError\",\"message\":\"{\\\"Code\\\":\\\"BadRequest\\\",\\\"Message\\\":\\\"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.\\\",\\\"Target\\\":null,\\\"Details\\\":[{\\\"Message\\\":\\\"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.\\\"},{\\\"Code\\\":\\\"BadRequest\\\"},{\\\"ErrorEntity\\\":{\\\"ExtendedCode\\\":\\\"14022\\\",\\\"MessageTemplate\\\":\\\"Input parameters are invalid. See details for more information. Details:{0}\\\",\\\"Parameters\\\":[\\\"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.\\\"],\\\"Code\\\":\\\"BadRequest\\\",\\\"Message\\\":\\\"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.\\\"}}],\\\"Innererror\\\":null}\"}]}}

It's the same input between the owner and the user, and the flow is triggered by a button in Powerapps.
When the user click on the button, it doesn't seem to trigger anything in powerautomate, since it doesn't appear on the history of the flow.

Again, the flow is shared ( execution only ) with the user of the app, i already tried to delete and reinstall the flow in the app, no change.

Thanks for all

UPDATE : i tried to add a new to the app, with no input parameters needed, and the same error occurs

UPDATE2 : i shared the test flow as a co-owner to the user and it worked - of course it doesn't resolve our case because then the user can modify the flow, but at least some improvement

Was this reply helpful? Yes No
Suggested answer

Tomac 3,950 Moderator on at

Like (0)

Report

@SS-18070931-0 @EL-29011114-0

In the Flow Information screen click Edit on Run Only Users:

Then in the Connections Used section, make sure your connections are not set to "Provided by run-only user" if they require specific permissions:

Was this reply helpful? Yes No
EL-29011114-0 15 on at

Like (1)

Report

@Tomac

On the flow test that i just add, it doesnt need any connection, so i don't think it's the issue,
And, if we use your solution ( which doesn't work, at least for me ), then the user will use the connection of the owner of the flow right ? ( which i don't want )

Thanks for your reply,

Happy to see that we have some help on that,

Was this reply helpful? Yes No
Tomac 3,950 Moderator on at

Like (0)

Report
@EL-29011114-0

Microsoft Copilot seems to know more about this error and suggest the following. It's worth a shot.

🔍 Why Non-Owners See the Error

When a flow is triggered by a non-owner, Power Automate may attempt to use their connection credentials rather than the owner's. If the flow or its custom connector expects a parameter like workflowAuthorization, but that parameter is only valid under the owner's context (or was never defined for general use), it throws an error.

Here’s what’s likely happening:

Owners have full access and their connections are authorized to use all parameters, including undocumented ones.

Non-owners trigger the flow using their own credentials, and Power Automate enforces stricter validation—rejecting parameters like workflowAuthorization that weren’t defined in the connector’s schema.

🛠️ How to Fix It

Use Owner’s Connection for All Users
In the flow settings, configure it to always use the owner’s connection rather than the caller’s. This ensures consistent behavior regardless of who triggers the flow.

Add workflowAuthorization as a Defined Parameter
If you want users to use their own connections, update the custom connector to explicitly define workflowAuthorization as a connection parameter.

Share the Flow with Run-Only Permissions
This limits what non-owners can do and ensures they don’t accidentally trigger unsupported actions.

Consider Using a Service Principal
For enterprise-grade flows, using a service principal as the owner avoids user-specific issues and ensures stable access control.

Was this reply helpful? Yes No
PT-19071544-0 2 on at

Like (0)

Report

I’m encountering a similar issue as you. It happens randomly with my users. Even though I’ve granted permission to connect to the admin account, the situation hasn’t changed. I’ve tried modifying the copy and co-owner settings, but it doesn’t seem to work. When reconnecting the flow after deleting it, I noticed an error message: "share_sharepointconnect." I suspect this might be the problem, but I haven’t found a solution.

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

Like (0)

Report

I have the same issue, but it only happens with some users, not all.

Everything was working fine before July 19th, and I only discovered the issue after one user reported a failure when using the app. After that, I started investigating and found that the flow was no longer triggered for certain users.

To isolate the issue, I created a simple test app and test flow:

1. The test app only have 1 button to trigger the test flow.

2. The test flow only contains a Power Apps V2 trigger and a Compose action.

I shared the app with the same user who had the issue, but the result was the same: they could not trigger the flow from the app and get the message:

Some strange things I noticed:
1. This user could run flows from the app normally before July 19.
2. The issue only happens with some users (3 users in my organization have encountered the same problem), not everyone.
3. When the problem happens, there is no run history in the flow. It's like the trigger never fired.
4. If I share the flow as Co-owner with the user, they can run it — but I don’t want to give everyone co-owner access. That’s not a good solution.

I don’t know why this started. Maybe something changed in Power Platform or Power Automate.
I hope someone can help explain or fix this issue.

Was this reply helpful? Yes No
CL-21070928-0 6 on at

Like (0)

Report

Where is your affected environment located?

We have two affected environments located in Germany. I migrated my Power App as well as the Flow to an environment located in Europe and the users affected by this issue did not experience any problems whatsoever.

Was this reply helpful? Yes No
KY-21071119-0 2 on at

Like (0)

Report

My client also has a similiar issue just today.

Over the last 1-2 weeks no issues. I tested the same setup at my company also no issue.
This is one of the error message. ALl revolving around WorkflowAutorization when Power Apps call Power Automate

Was this reply helpful? Yes No