Power Platform Community Forum Thread Details

I have a Power Automate flow that triggers on Dataverse record updates, but it executes twice consecutively for the same record modification, even with concurrency control enabled.

Flow Configuration

Trigger: When a row is added, modified or deleted (Dataverse)

Entity: dc_dailyotstats

Scope: Organization (4)

Filter Expression: dc_iscompleted eq true and dc_isprocessed eq false

Filtering Attributes: dc_iscompleted,dc_isprocessed

Concurrency Control: Enabled with Degree of Parallelism = 1
The Problem

When another flow sets dc_iscompleted = true at 8:00 PM, my flow executes twice at the exact same time (e.g., 20:06:00 and 20:06:00).

Example from execution history:
Execution 1: Start time: 20:06 - Duration: 00:00:17 - Success

Execution 2: Start time: 20:06 - Duration: 00:00:17 - Success

Categories:

Power Automate Desktop

Hi,

This happens because Dataverse may fire both a Create and an Update event for the same row, so Added, modified or deleted can trigger twice.

Change Change type to only the specific event you need for example, Modified only.

Keep Filtering attributes to only the fields that should trigger the flow dc_iscompleted, dc_isprocessed) so child/related updates don’t re-trigger it.

Add a trigger condition like @equals(triggerOutputs()?['body/dc_isprocessed'], false) so if a first run sets it to true, a second parallel trigger immediately exits.

Also double‑check there isn’t a second copy of the same flow or similar trigger in another environment or solution

If I have answered your question, please mark it as the preferred solution ✅ . If you like my response, please give it a Thumbs Up 👍.
Regards,
Riyaz