Skip to content

Power Automate

Why is my Power Automate flow not triggering?

By Suresh Girinathuni

Quick answer

Common causes include incorrect trigger configuration, trigger conditions evaluating to false, connection problems, permissions, changed source data, environment configuration or the event not satisfying the trigger criteria. Check the trigger and flow run history before modifying downstream actions.

Key takeaways

  • Check flow On/Off state, connections, and trigger run history first.
  • Trigger conditions evaluating to false is the most common silent cause.
  • Permissions, drafts, and bulk updates can prevent trigger events.

Detailed Explanation

Common causes include incorrect trigger configuration, trigger conditions evaluating to false, connection problems, permissions, changed source data, environment configuration or the event not satisfying the trigger criteria. Check the trigger and flow run history before modifying downstream actions.

How it works

Every run starts with a trigger evaluation. SharePoint and Dataverse triggers poll or webhook on specific events (created, modified, column change). If trigger conditions filter the event out, or the connection owner lost access, no run is created — so there is nothing in run history to debug except the trigger itself.

Limitations and considerations

Some triggers do not fire on system updates, bulk migration writes, or changes made by service accounts without the right permissions. Checked-out files, draft items awaiting approval, and disabled flows also silently skip triggers.

This Q&A page is the short-answer layer for “Why is my Power Automate flow not triggering?” Use the related guides below when you need implementation steps, architecture trade-offs, or troubleshooting detail.

For broader context, visit the Power Automate Hub. It connects this topic to surrounding Microsoft 365, Power Platform, SharePoint, Copilot Studio, Dataverse, migration, and Dynamics 365 guidance.

When to use it

Use this checklist when a flow shows zero runs after a SharePoint, Dataverse, or Teams event you expected to fire it.

Practical example

A “when an item is created” flow never fires because the list uses required approval and items stay in Draft. Publishing the item (or widening the trigger to handle drafts) produces the first run.

Related Questions

How should errors be handled in Power Automate?Enterprise flows should use structured error handling with scopes, run-after rules, logging, notifications, and retries where appropriate.What is Power Automate?Power Automate is Microsoft’s cloud automation platform for creating workflows between apps, services, data, and APIs.Can Power Automate call REST APIs?Yes — prefer a purpose-built connector first, use the HTTP action for direct REST calls, and package repeated integrations as custom connectors. Authenticate with Entra ID identities and handle errors explicitly.What is Power Automate best used for?Power Automate shines at approvals, notifications, SharePoint and Dataverse data sync, scheduled jobs, and Microsoft 365 glue work — repeatable processes owned by business teams, not integration platforms.

Related nextM365 Guides

Power AutomatePower Automate Error Handling: Build Reliable FlowsLearn how to build reliable Power Automate cloud flows with run after settings, Try Catch Finally scopes, retry policies, error logging, notifications, validation, and monitoring.Power AutomatePower Automate Cloud Flows Explained: Complete Beginner GuideLearn the basics of Power Automate cloud flows, including automated, instant, scheduled, and business process flow examples for beginners.

Sources