Trigger is not firing – The trigger conditions are not being met.

Triggers are essential in Power Automate, as they determine when a flow starts. However, users sometimes encounter the following issue:

“Trigger is not firing – The trigger conditions are not being met.”

This means the flow is not starting as expected, likely due to incorrect configurations, permissions, or external service limitations.

2. Causes of the “Trigger is Not Firing” Issue

This issue can arise due to several factors, including:

Trigger Conditions Not Being Met – If specific trigger conditions are defined, but the incoming data does not match them, the flow will not start.
Trigger Type Mismatch – The trigger may be incorrectly configured (e.g., using a manual trigger instead of an automatic one).
Permissions Issues – The user or flow owner might not have the required access to the connected resource.
Data Source Issues – If the trigger is based on an external service (e.g., SharePoint, Outlook, Dataverse), it may not be receiving updates properly.
Flow Turned Off or Suspended – If the flow is disabled, suspended, or has reached execution limits, it will not fire.
Power Automate or Service Downtime – If Microsoft services (e.g., SharePoint, Outlook, Dataverse) are down, the trigger will not fire.
API or Connector Limitations – Some connectors have polling intervals or event limitations that may delay or prevent triggering.
Changes in Environment Variables – If the flow depends on environment variables and they have changed, the trigger might not function correctly.

3. Step-by-Step Troubleshooting Guide

Step 1: Verify the Flow’s Run History

Go to Power Automate (https://flow.microsoft.com).
Click on My Flows and locate the flow in question.
Select Run History to check if the flow has executed.
If there are no entries, the trigger is not firing.

Step 2: Manually Test the Trigger

If the trigger is a manual trigger, click Run Flow and see if it starts.
If the trigger is an automated trigger, perform the expected action (e.g., add an item to SharePoint, receive an email).
If nothing happens, move to the next step.

Step 3: Check Trigger Conditions

Open the trigger and look for “Trigger Conditions” under Settings.
Ensure the condition syntax is correct.

✅ Correct Example (Trigger only when Status = ‘Approved’):

@equals(triggerBody()?['Status'], 'Approved')

❌ Incorrect Example (Extra spaces, missing quotes):

@equals(triggerBody()? [ Status ], Approved)

If the trigger condition is too strict, try removing it temporarily and testing the flow.

Step 4: Verify Data Source Changes

If using a SharePoint trigger, check if items are being created or modified as expected.
If using an email trigger, ensure the email is received in the correct folder.
If using a Dataverse trigger, verify that the target entity is updating.

Step 5: Check Permissions and Ownership

Ensure that the flow owner has the necessary permissions to the resource.
If using a SharePoint trigger, the flow owner must have at least Edit permissions.
If using a Dataverse trigger, the flow owner must have appropriate access to tables and data.

To verify permissions:

Go to Power Automate > My Flows.
Click on the flow and go to Details > Owners.
If necessary, add or update permissions.

Step 6: Confirm the Flow is Enabled and Not Suspended

Go to Power Automate > My Flows and check the flow status.
If the flow is turned off, turn it back on.
If the flow is suspended due to exceeding limits, consider optimizing it or upgrading your Power Automate plan.

Step 7: Check for Service Outages

Visit Microsoft 365 Service Health (https://status.office.com).
If the service linked to the trigger (e.g., SharePoint, Outlook, Dataverse) is down, wait for Microsoft to resolve the issue.

Step 8: Review API and Connector Limitations

Some triggers, like When an item is created or modified, use polling mechanisms that check for changes every few minutes.
If using a premium connector, ensure your subscription supports it.
Check Power Automate documentation for trigger-specific limitations.

Step 9: Recreate the Trigger

Delete the trigger from the flow and add it again.
Save and test the flow.
If the issue persists, create a new flow with the same trigger and test it separately.

Step 10: Enable Notifications and Logging

In Settings, enable Trigger Failed Notifications to receive alerts when the trigger fails.
Add a Scope action in the flow to capture errors and log them to SharePoint or an email.

4. Preventative Measures

To avoid future trigger issues:

✔ Use Test Data – Regularly test triggers with sample data.
✔ Check Flow Activity – Monitor run history for patterns in failures.
✔ Use Default Values – Prevent null errors with coalesce().
✔ Stay Within Limits – Avoid hitting Power Automate execution limits.
✔ Monitor Microsoft Services – Subscribe to service health notifications.
✔ Keep Permissions Updated – Ensure all required access is in place.