Microsoft Dynamics 365 | Integration, Dataverse...

Error 0x80045052 when calling a flow from Power Apps

(0) Share

Report

Posted on by CU10040730-0

When executing a Power Automate flow from a Canvas App in the UAT environment, an error is encountered:

**Error Code:** `0x80045052`
**Error Message:** *The process action associated with this process is not activated.*

This issue is affecting a subset of users—some are able to run the flow successfully, while others are consistently encountering the error. The inconsistency suggests a potential issue with user permissions, environment configuration, or flow activation status.

Environment: UAT
Urgency: High – Business users are scheduled to begin UAT testing tomorrow.

Troubleshooting Steps Taken:
1. Used **Live Monitor session** to trace the issue. see attached log file.
2. Utilized **XRMToolBox Impersonate** to simulate affected users.

Fix Attempts:
**Canvas App:**
- Verified button configuration.
- Republished the Canvas App.

**Power Automate Flow:**
- Refreshed the flow.
- Removed and re-added the flow to the Canvas App.
- Created a new connection.

Categories:

Dynamics 365 general

Power Platform integration

image (40).png

I have the same question (0)

All responses (2)

Answers (0)

CU10040730-0 2 on at

Like (0)

Report

Error 0x80045052 when calling a flow from Power Apps

Hello Daniele,

Thank you for the swift response.

I have tried all of these, yet the issue still persist.

Was this reply helpful? Yes No
Suggested answer

DAnny3211 10,787 Moderator on at

Like (0)

Report
Error 0x80045052 when calling a flow from Power Apps

Hi,

The error 0x80045052 – "The process action associated with this process is not activated" typically indicates that the Power Automate flow being called from your Canvas App is either not activated or not properly associated with the triggering action in the environment.

Given that some users can run the flow while others cannot, here are a few targeted steps to help resolve the issue:

Check Flow Activation: Ensure the flow is activated and published in the UAT environment. Sometimes flows appear active in the designer but are not properly deployed.

Verify User Permissions: Confirm that all affected users have the necessary permissions to execute the flow. This includes access to the Dataverse tables and any connectors used in the flow.

Environment-Specific Connections: Make sure the flow connections are valid for the UAT environment. Re-authenticate or recreate connections if needed, especially if the flow was copied from another environment.

Security Roles: Check if the users encountering the error lack a required security role that grants access to the process or entity involved.

Flow Ownership: Ensure the flow is owned by a user or service principal with sufficient privileges. Reassigning ownership can sometimes resolve activation issues.

Re-add Flow to App: As you've already tried this, consider creating a minimal test flow and linking it to the Canvas App to isolate whether the issue is with the flow logic or the app integration.

Please verify if this helps address the issue before UAT begins.

Thanks and best regards,

Daniele

Note: This response was prepared with support from Copilot to ensure clarity and completeness.

Was this reply helpful? Yes No