TWL-KB-021 · Power Automate · Maker / builder

A flow runs twice or creates duplicates

Compare run IDs and source events before disabling production flows.

Applies to: Power Automate cloud flows.

Revision 5 · 18 November 2026 · General first-line guidance. Wording varies by version; a symptom is not a confirmed diagnosis.

Two runs / duplicate items (symptom). Compare run IDs and source events before disabling production flows.
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

What does the message mean?

Some rows describe a visible symptom rather than an exact message. Wording marked “varies” may differ on your screen.

What you seeWhat it may indicateWhat to check
Two runs / duplicate items (symptom)Several source events, trigger design or a replay may be involved. Duplicates do not prove a platform fault.Compare run IDs and source events before disabling production flows.
No message at allProblems can happen without any message. A blank screen or a missing control is still useful evidence.Record the visible behaviour, the time and who is affected. Do not guess a code.
First checks: Compare run IDs; Compare source events; Identify what was created; Ask for a controlled fix
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

Step-by-step checks

Work in order and stop when it is resolved. If your screen differs, note what is different and ask IT or the owner.

  1. Compare run IDs

    Do this
    Find the runs and note their times and trigger identifiers.
    What you should see
    There are separate runs, or repeated actions inside one run.
    Then what?
    If this explains what you see, record it and continue only if the next check still applies.
  2. Compare source events

    Do this
    Check whether the source item was created, edited or submitted more than once.
    What you should see
    The events match or differ.
    Then what?
    Record the result without changing settings. Stop if work, data or security could be affected.
  3. Identify what was created

    Do this
    List records or messages already created without deleting them.
    What you should see
    You know the extent of the duplication.
    Then what?
    Use only the approved action described here. If it does not match your screen, stop and ask IT.
  4. Ask for a controlled fix

    Do this
    Ask the owner to review trigger conditions and duplicate prevention in a test copy.
    What you should see
    There is a test plan that does not disrupt live work.
    Then what?
    If unresolved, contact IT or the owner with sanitised evidence. Do not repeat actions that could duplicate data.

When to stop and contact IT or the owner

What to put in your support request

The app and version if visible, your device, the time, the exact message, who is affected, and the checks you tried with what you saw. Remove names, addresses and confidential content from screenshots. Never send passwords or MFA codes.

Microsoft reference

Microsoft documentation for this topic (opens a new tab). Some links are product hubs. Official pages may include advanced steps; ask IT before applying them on a managed device.

Related guides

The Workflow Lab is independent of Microsoft and is not your employer’s service desk.