Flow triggering multiple times

(1) Share

Report

Posted on by KP-19021713-0 Microsoft Employee

I have a flow that sends an email when the status of a column is updated to a specific status and the concurrency control is set to 1. At the end of the flow it flips a flag in a different column to indicate the email has been, so that if it tried to send another, the condition in the flow checks the status of that column too before pushing the email out. Yesterday 4 different rows were updated in rapid succession and caused 3 emails to be sent out per person. What else can i do to prevent this from occurring?

Categories:

Building flows

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Suggested answer

Pstork1 69,270 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

You need to add the check on the column that indicates the email has been sent to a trigger condition. That will prevent it from re-triggering.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Suggested answer

11manish 1,196 on at

Like (0)

Report
Copy link

Link copied!
Concurrency = 1 only controls parallelism inside a trigger, not event deduplication

Your duplicates happened because:

Multiple flow runs started before the flag was updated

Best fix:

Add trigger condition

Recheck flag using Get row

Update flag before sending email

Was this reply helpful? Yes No
Suggested answer

Haque 1,758 on at

Like (0)

Report
Copy link

Link copied!

Hi @KP-19021713-0 ,

What is your initial trigger in the PowerAutomate, and is it a SP list? It seems like your condition is not fulfilling and triggering multiple times when you go to update the status again (flip the status). Can you please show how you have written the flip expression?

If it is happening in the production environment I would suggest stop the flow, it will create bad impression to the customers/users until it is fixed. Also, taking another list - replicate the flow ( no copy), just manually build again and test with your account first - this will help to identify any peccadilo is there in the syntax.

Was this reply helpful? Yes No
KP-19021713-0 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@Haque, it's a SP list, should i move to a dataverse table? This is the code from the trigger.

{

"type": "OpenApiConnection",

"description": "Trigger only when the Status column is updated to 'Employee invited'.",

"inputs": {

"parameters": {

"dataset": "https://microsoft.sharepoint.com/sites/EmployeeExecutiveSocialCommunications",

"table": "edd62070-e563-4e15-9c36-04e3197f07d7"

},

"host": {

"apiId": "/providers/Microsoft.PowerApps/apis/shared_sharepointonline",

"connection": "shared_sharepointonline-1",

"operationId": "GetOnUpdatedItems"

}

},

"recurrence": {

"interval": 1,

"frequency": "Minute"

},

"conditions": [

{

"expression": "and(@equals(triggerBody()?['Status/Value'], 'Employee invited'))"

},

{

"expression": "and(@equals(triggerBody()?['InviteEmailSent_x003f_/Value'], 'No'))"

}

],

"runtimeConfiguration": {

"concurrency": {

"runs": 1

}

},

"splitOn": "@triggerOutputs()?['body/value']",

"metadata": {

"operationMetadataId": "7eed98d9-b22d-40ee-b78f-fa2a5801958a"

}

}

Was this reply helpful? Yes No
Pstork1 69,270 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Moving to a Dataverse table wouldn't solve the problem you are having. What kind of column do you record that the email has been sent in? If you give me the details of that column I can explain how to add a trigger condition that will keep it from triggering when that value is set in the previous flow.

Based on what you posted it looks like you've already tried adding some trigger conditions, but those will be handled by default as an 'OR' condition. To prevent the re-triggering it needs to be an AND. to do that you need to do it as a single condition.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
KP-19021713-0 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@Pstork1, the code is from the only the trigger, which I've added those two conditions as part of the setting. I do have another condition later on that is an "and" condition. The column where the "Status" is updating is a 'Choice' column.

Was this reply helpful? Yes No
Suggested answer

Pstork1 69,270 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Your screenshot is showing a Condition action in the flow. By then the flow has already been triggered. I'm talking about creating a Trigger Condition in the Settings of the Trigger. You can see it in the screenshot below:

That will prevent the flow from triggering at all unless both of those conditions are met.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No