How to Fix Power Automate Triggers Not Firing

TL;DR: Fix Power Automate triggers by checking flow status, the actual trigger error, connections, conditions and connector scope, then verify with a new matching event.

Checked 29 October 2026. Start with run history: no run and a failed action point to different faults. Record the environment, trigger name and test-event time before changing the flow; otherwise a successful manual run can hide an event-detection problem.

Where should you start when no run appears?

Open the flow in the intended environment and check whether it is On, Off or Suspended. Microsoft's connection troubleshooting guide starts with status and run history. If a run exists, inspect its trigger and first failing action before rebuilding the trigger.

For an automated flow, create a fresh item or file in the exact watched resource. For an instant flow, use its configured button or app. Polling connectors check periodically, so allow the documented interval rather than expecting every event immediately. Use the trigger overview to confirm the flow type.

Why is my Power Automate trigger not firing?

1. Is a data policy blocking the flow?

Symptom: The flow is suspended or saving reports an organisation policy violation.

Diagnostic: Read the specific flow checker message. Save errors can come from invalid expressions or missing fields as well as policy violations.

Fix: Ask the administrator to review the applicable data policy and permitted connector use. Make the flow comply with the policy, or ask for an approved policy change.

2. What does the trigger error actually say?

Symptom: The details page displays "There's a problem with the flow's trigger."

Diagnostic: Select Fix the trigger and inspect the underlying error. Microsoft's banner troubleshooting article includes a missing SharePoint folder, invalid inputs and connection failures; the banner does not identify a firewall fault by itself.

Fix: Repair the named resource or connection. When evidence points to blocked traffic, IT should check the applicable Power Automate network requirements. After fixing the cause, save a setup change and restore it if re-registration is needed.

3. Is the connection broken or missing permission?

Symptom: A previously working flow stops after account, credential or access changes.

Diagnostic: Open More > Connections, or Connections in the navigation, and inspect the actual connection used by the trigger. Check its account can still access the selected site, folder or mailbox.

Fix: Use Fix connection or re-authenticate when prompted, then retest. Check resource permission separately after signing in; use the Power Automate 401 and 403 guide for that distinction.

4. Does the event satisfy every trigger condition?

Symptom: The source changes, but no flow run starts; a trigger check may appear as skipped.

Diagnostic: Select the trigger, then Settings > Trigger conditions in the new designer. The classic designer uses the card's ellipsis menu. Compare field names, values and types with a known event payload.

Fix: Correct the expression and test one matching and one nonmatching event. Microsoft's condition documentation says false trigger conditions create no run-history entry, and multiple entries require all conditions by default. A downstream Condition action runs after the trigger and has different history.

5. Do recurrence settings match the intended schedule?

Symptom: The flow runs at an unexpected time or has not reached its next scheduled occurrence.

Diagnostic: Inspect Start time, Time zone, Interval and Frequency, plus the day/hour/minute options where applicable. The scheduled cloud-flow guide explains these settings; a historical start date alone does not prove the trigger is broken.

Fix: Configure the intended business time explicitly, save, and observe a future scheduled occurrence. The Z suffix denotes UTC. Do not repeatedly move the start time or promise that missed scheduled executions will all replay.

6. Which SharePoint trigger and folder scope are selected?

Symptom: Files created in part of a library do not start the flow.

Diagnostic: Read the exact operation name in the SharePoint connector reference. The deprecated "in a folder" file triggers explicitly exclude subfolder events; that limitation must not be applied to every SharePoint trigger.

Fix: For a current library-based workflow, evaluate When a file is created or modified (properties only). Its Folder parameter can be left blank for the whole library; test a root file and a nested file in a copy before migrating. Recheck filters and downstream dynamic-content references.

What else can stop a trigger?

Check licence requirements and environment state when the six checks do not explain the failure. Dataverse triggers depend on background operations, so administration mode with those operations disabled can stop them while recurrence and unrelated connectors continue. Microsoft's trigger diagnostics distinguishes this case.

The cloud-flow limits also describe automatic turn-off after continuous errors or throttling and inactivity rules with licence exceptions. Use the status and notification to identify why the flow stopped. Check service health and observed delay before repeatedly recreating a production flow.

How do you find a misfiring trigger in five minutes?

1. Confirm the environment, flow status and whether a recent run exists.
2. Read policy messages and the underlying trigger error before changing settings.
3. Repair the selected connection and verify resource permissions.
4. Compare trigger conditions with a real matching event.
5. Check the intended recurrence time and the exact SharePoint operation and folder scope.
6. Record a fresh event's timestamp, wait for the relevant check, and inspect the resulting run.

Use a harmless test action or a safe copy when an event could send messages or update records. Compare the source event, trigger output and action result. A green manual test does not by itself prove the original automated subscription or schedule works.

What happens when you re-enable a flow?

Resume behaviour depends on the trigger. Microsoft's diagnostics distinguishes polling backlogs from new webhook events; this does not establish that every missed recurrence occurrence will replay. Preserve the existing definition and test with identifiable events, with safeguards for duplicate side effects.

If a specific error remains, use the Automation Error Index to find the matching guide. Save the event time, trigger name and error details for an administrator or support case.

FAQ

Why does my Power Automate flow stop triggering after a few weeks?

Check flow status and connection health before picking a cause. Credential changes, permissions, policy enforcement, repeated failures and licence-dependent limits need different fixes.

What does "There's a problem with the flow's trigger" mean?

Open the linked trigger error to identify the failing input, connection or registration. Microsoft also documents a stale banner after successful events, so verify a fresh run rather than treating the banner alone as proof.

Why doesn't my recurrence flow run on schedule?

Check its enabled state, start time, time zone, frequency and interval. Verify a future scheduled occurrence; a past start date alone does not establish failure.

Why doesn't my SharePoint trigger fire for files in subfolders?

Check the exact trigger: deprecated folder operations exclude subfolders. Current properties-only library triggers expose a Folder selection that can be blank for the whole library; test the intended scope before replacing the original flow.

Does turning a flow off and on re-run old events?

Some polling triggers can process pending events, while webhook handling differs. Check the selected trigger's documented resume behaviour and protect downstream actions against duplicates.