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

Cloud flow did not trigger

Confirm the right flow and environment before editing the trigger.

Applies to: Power Automate cloud flows; options depend on your environment and licence.

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

No new run in run history. Confirm the right flow and environment before editing the trigger.
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
No new run in run historyAn absent run is different from a failed action. The trigger, connection, conditions, environment or licensing may need review.Confirm the right flow and environment before editing the trigger.
Flow is turned off / suspended (wording varies)The flow may not be running at all.Check the flow status and ask the owner. Do not turn it on without understanding what it will process.
SkippedAn action did not run, possibly due to an earlier outcome or branch.Check the earlier actions and run-after settings in a copy, not the live flow.
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: Find the intended flow; Check the expected event; Inspect run history; Note connection warnings
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. Find the intended flow

    Do this
    Open the intended environment and flow, and compare its name and owner with your documentation.
    What you should see
    You can identify the correct flow and its state.
    Then what?
    If this explains what you see, record it and continue only if the next check still applies.
  2. Check the expected event

    Do this
    Note when the source event happened and compare it with the trigger and its filters. Do not edit them yet.
    What you should see
    The event matches the trigger, or a condition may exclude it.
    Then what?
    Record the result without changing settings. Stop if work, data or security could be affected.
  3. Inspect run history

    Do this
    Review the time range around the event.
    What you should see
    No run exists, a run was delayed, or an action failed inside a run.
    Then what?
    Use only the approved action described here. If it does not match your screen, stop and ask IT.
  4. Note connection warnings

    Do this
    View the connection status and exact warning without switching accounts.
    What you should see
    A sign-in warning is shown, or connections look normal.
    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.