Microsoft Dynamics 365 | Integration, Dataverse...

When updating Process Logs - Bad Request

(1) Share

Report

Posted on by Power Platform Comm...

Hi All,

I have created a business process flow which is integrated to model driven app in which user need to trigger a power automate flow to send an approval email. When I trigger the flow In order to update the status of the power automate workflow in Business Process Flow(BPF) I'm trying to update the 'Process Logs' Entity as the last action. This all process is working fine for the admin role but when I'm changing the role to normal role and triggering the last step fails i.e (update the record in the process logs status as succeeded )

Error In the Workflow:

--batchresponse_82c740ed-78a6-49a8-ae6c-71d36cd6f39c
Content-Type: application/http
Content-Transfer-Encoding: binary

HTTP/1.1 400 Bad Request
REQ_ID: 7b7a6589-53d7-4ce4-b4be-e31a13e5d2e8
Content-Type: application/json; odata.metadata=minimal
OData-Version: 4.0

{"error":{"code":"0x80040530","message":"Unable to retrieve attribute=ownerid for entityLogicalName=asyncoperation. Entity has Attribute Count=2. AttributeNames= status, workflowlogid"}}
--batchresponse_82c740ed-78a6-49a8-ae6c-71d36cd6f39c--

Could anyone please help me or provide any work around?

Thank you!

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Power Platform Comm... 8 on at

Like (0)

Report
Copy link

Link copied!

Hi

Looks like its a permission issue for me. So for updating the process logs can't you use an integration account?

Thanks

Was this reply helpful? Yes No
Kessi 5 on at

Like (0)

Report
Copy link

Link copied!

I also have this issue. Any ideas? It seems like a missing permission in the security role. Admin can do this and normal app user cannot.

Which security role permission gives the user access to read/write/append the workflow process logs?

Was this reply helpful? Yes No
Power Platform Comm... 8 on at

Like (0)

Report
Copy link

Link copied!

So I am having the same issue. If we make the account a systemadmin the individual can run the flow without issue, however as soon as they aren't a system admin it errors out with the same error code. But I can't even locate where the entity lives workflowlogid to look at permissions for it. Is there any help as far as assigning permissions for that specific entity and where to find and how to do it?

Was this reply helpful? Yes No
EB-22060108-0 2 on at

Like (0)

Report
Copy link

Link copied!

Hello Community. I see in this thread that there was never an answer posted from Microsoft or community experts. Is there a newer thread that has the answer/resolution on how to get a non System Administrator or System Customizer to be able to successfully complete an automate flow from within the BPF so that the stage unlocks and is able to be advanced to the next stage if the flow is set as required. As of June 2026 I have not been able to find the correct sequence of permissions and/or available tables to grant permissions to a basic user that does not need to have sysadmin privileges to us my model driven app. I have been using Copilot and Claude and we still have not solved the problem. I'm operating in the GCC controlled by the IT divisions which is a little more restrictive but it sounds like basic MS user's have been having this problem too since 2021.

Thank you for your time and assistance.
Eric B.

Was this reply helpful? Yes No
Suggested answer

11manish 1,079 on at

Like (0)

Report
Copy link

Link copied!

The error is most likely caused by the normal user lacking Read access to the AsyncOperation (System Jobs) table or related system records. I recommend first reviewing the user's security role and testing with a custom role that has additional read privileges on the relevant system tables. If the goal is simply to indicate that the approval flow has completed, a more robust and supported design is to store that status in a custom table or the primary business record, rather than updating the system-managed Process Logs entity. This approach is easier to secure and less likely to be affected by platform restrictions.

Was this reply helpful? Yes No