Email Triggering multiple times

(0) Share

Report

Posted on by RK-03060544-0

I have built a Power Automate flow using the “When an item is created or modified” trigger.

My requirement is: when a specific column (Status) changes to “Completed”, a completion email should be sent to the client.

However, the issue is that the email is triggering multiple times, even though the condition is applied.

I have already tried the following approaches:

Added a Condition to check if Status = Completed
Used a Delay action
Updated the Status column after sending the email to avoid re-trigger
Tested with a simplified condition setup

But still, the email keeps triggering multiple times.

To simplify, I even tested with a very basic condition setup, but the issue still persists.

Could someone please help me understand why this is happening and how to fix it?

Screenshot 2026-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

David_MA 14,918 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Have you used a trigger condition to set up the flow so that it only triggers when status equals completed? If not, you can learn about trigger conditions here: Customize your triggers with conditions - Power Automate | Microsoft Learn. All trigger conditions must evaluate to true for the flow to run.

The easiest way to create a trigger condition is to add a compose action after the trigger. Then write an expression that returns a Boolean true/false value. You can then copy the expression and add @ before the expression to create the trigger condition. Keep in mind, as I noted, the expression must return true for the flow to trigger. It will not trigger if the expression returns false.

If you've already done this that only solves half the problem. If the form is edited later and the status is still Completed, it will trigger again. This will even happen if your workflow is updating the item. Therefore, you need to have two conditions to prevent the flow from triggering again.

For example, you could add field name Completed Notification Sent with a default value of no. Since this is a Boolean field and you've set the default value to false, you can just insert the dynamic value preceded by an ampersand: @triggerOutputs()?['body/CompletedNotificaationSent']

When the flow runs, update the Completed Notification Sent field to true, and that will prevent the flow from triggering again.

Was this reply helpful? Yes No
RK-03060544-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

I have tried with the mentioned approach, but it is not helpful.

I have tried to stop the recurrence mails by cascading the SP list columns to excel sheet, but for different kind of selections different email patterns have to be triggered.

Is this requirement acheiveble?

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

Like
a
(0)

Report
Copy link

Link copied!

Please share a screen shot of your workflow showing the configuration of the trigger condition, and also how you update the secondary field to prevent a recurrence. Here is an example of what I mean:

Trigger condition:

@and(equals(triggerOutputs()?['body/WorkflowStatus/Value'],'Pending'), equals(triggerOutputs()?['body/Submitted'],'Submitted'))

The flow will only trigger if the Workflow Status is Pending AND Submitted equals Submitted.

I then use an HTTP request to change the value of the Status to something else so that the flow cannot trigger again:

In the above, it changes the status to Manager Approval. That value actually triggers another workflow and when that flow runs, it changes the Workflow Status to Manager Approval Pending so it cannot trigger again.

Note: you can of course use the regular update an item action rather than an HTTP request to update the values.

Was this reply helpful? Yes No