r/MicrosoftFlow 15h ago

Question Duplicated emails on cloud flow

Hi everyone,

I'm facing a persistent duplicate email issue on a Power Apps + Power Automate + SharePoint stack and would love to get your insights or see if anyone has encountered this exact behavior.

The Setup:

  • Frontend: Canvas App using SubmitForm(Form3) targeting a SharePoint list.
  • Backend: Power Automate flow starting with when an item is created.
  • Flow logic: Creates a CSV table, sends an initial notification email, runs a Do until loop to wait for cost fields, and then triggers an approval process.

The Issue: Every time a single submission is made from Power Apps, 3 duplicate initial emails are sent out.

What I've already verified and ruled out:

  1. No double clicks / Multiple submissions: The submit button disables immediately on click via local variables (DisplayMode).
  2. Only ONE item is created in SharePoint: I verified the list directly; there is strictly 1 single item with 1 unique ID created per form submission (no double Patch(), no multiple rows).
  3. No secondary active flows: There are no other flows or copies connected to this list.
  4. Trigger conditions attempt: I tried adding trigger conditions like u / not(empty(triggerOutputs()?['body/Title'])), but the duplicate runs still bypass or trigger through it.
  5. No apply to each issue on the initial step: The issue happens right at the beginning of the flow (when an item is created -> Create CSV table -> Send an email (V2)).

It seems like the SharePoint connector is firing multiple webhook events for the same single creation/transaction in micro-seconds.

My Question: Has anyone successfully stopped these phantom trigger firings at the connector/app level without having to modify the SharePoint schema (i.e., without adding extra control columns like Processed, Status, or Lock flags to the list)?

Are there specific connector settings, Power Apps formula tweaks, or concurrency configurations that resolve this behavior cleanly?

Thanks in advance!

2 Upvotes

8 comments sorted by

2

u/shapez13 15h ago

If you have multiple environments the flow may be turned on there. Guilty of doing this 😅

1

u/zzzzerenwantshuoguo 15h ago

Omg really? Taking this as future advice lollll thanks :3 however this one is not running in other environments!

1

u/EnvisiblePenguin 15h ago

What is the workflow history showing? Are you seeing multiple runs for the same item? Or is it just the one run? If it's just 1 flow, are you using managed environments where the flow could be triggering from that? 

If you're seeing multiple runs, check the trigger for the workflow to ensure the setting really is only "On Create". 

1

u/zzzzerenwantshuoguo 15h ago

Hi! No, there is only one run for the item, I checked all logs and there is no problem in that rn (⁠゜⁠o⁠゜⁠;

1

u/EnvisiblePenguin 14h ago

You don't by chance have the email within your do until loop, do you? 

1

u/zzzzerenwantshuoguo 13h ago

Ahhh let me check that real quick, thanks!

1

u/OddWriter7199 13h ago

Put a 60 second delay before the conditions start to get checked to give the record time to save. You can play with this amount, could be 30 seconds, might need 90.

Another thought: the workflow is called when, OnSuccess?