Power Automate

Dataverse When a row is added, modified, deleted Not Triggering

(1) Share

Report

Posted on by David_MA

14,605 Super User 2026 Season 1

I created a flow with the Dataverse trigger When a row is added, modified or deleted with the following configuration:

There is no trigger condition. I have initiated a number of approvals, completed them, and even manually updated rows in the approvals table, and the flow is not triggering. The account owner of the flow is a service account and has the Environment Admin role. Any ideas?

For context, I am trying to create an approval process that can extend beyond the 28-day limit and am following the instructions in https://www.matthewdevaney.com/extend-a-power-automate-approval-over-the-30-day-limit. If you have another way to do this, I am open to other methods as well.

NOTE: I created the flow in one of my other environments and it works there. I am thinking it is an environment configuration issue, but I cannot figure it out yet. I have one of our other admins taking a look to see if he can see something I am missing.

Kind regards,

David

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

David_MA 14,605 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

I found that the issue with my Power Automate flow triggering on Dataverse row changes was due to webhook corruption, which can happen because of high concurrency, network issues, or misconfigurations. To fix this, I enabled concurrency control in the trigger settings to limit the number of instances of the flow runs at a time, which helps refresh the webhook.

Was this reply helpful? Yes No
LH-13031502-0 4 on at

Like (1)

Report
Copy link

Link copied!

Hi David,

I came across your post while searching for a solution to an issue with my Power Apps cloud flow that uses a Dataverse trigger. The flow is registered on Case creation as part of an Email-to-Case process.

It seems that a larger volume of incoming emails may have caused the flow not to trigger for all created cases. For example, when about 10 cases were created within one minute, 3 of them did not trigger the flow.

In your comment, you mentioned “webhook corruption, which can happen because of high concurrency, network issues, or misconfigurations.” While I understand that such issues can occur, the statement has significant implications for how reliable flows are under load. It almost suggests that flows may not be suitable once there are more than just a few triggers per minute.

Because of that, I’m quite concerned about this statement and would like to better understand how you came to this conclusion. Is this based on documented behavior, internal guidance, or personal experience? Are there any official Microsoft statements or documentation that confirm this?

Also, regarding the fix you described: could it potentially lead to a queue over-expansion or other side effects, such as a growing backlog of events?

Thanks in advance for any clarification you can provide.

Kind Regards

Lukas

Was this reply helpful? Yes No
David_MA 14,605 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hello LH-13031502-0 . I am going to assume I wrote the response above back in November 2024, but it doesn't sound like something I wrote. I know they had to migrate messages in the forums in that time. I need to head to a meeting, so hopefully I will come back and to update this post with more details. But to have an endless window for approvals, the action needs to be set up like this:

statuscode eq 192350004 — means the approval action has been completed.

msdyn_flow_approval_source eq 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' — this is a unique ID you update the approval with after it has been sent. I set it to the same workflow ID as the workflow that sends the approval.

I then have a field in the SharePoint list that stores the Approval ID of the approval. When this flow triggers, it uses a get items action on the SharePoint list to return the item with the same approval ID.

Was this reply helpful? Yes No