Troubleshoot common issues with triggers - Flow

My trigger doesn’t fire

1. A data loss prevention policy could be to blame.

   Admins can create data loss prevention (DLP) policies that can act as guardrails to help prevent users from unintentionally exposing organizational data. DLP policies enforce rules for which connectors can be used together by classifying connectors as either Business or Non-Business. If you put a connector in the Business group, it can only be used with other connectors from that group in any given app or flow.

   If your flow violates a DLP policy, it will be suspended, causing the trigger to not fire. To know if your flow is suspended, try to edit the flow and save it. The Flow checker will report it if the flow is violating a DLP policy. Your admin can change the DLP policy.

2. The trigger may be failing.

   To confirm:

   1. Go to My flows and then select your flow.

   2. Do you see the following error in the Details?

      

   This error means that Power Automate tried multiple times to establish a connection to register the trigger and failed. Your flow won't trigger until this problem is resolved.

   One of the common reasons for the failure is that the Power Automate service end points are not part of the allow list. To fix it, confirm that your IT department has added these endpoint to the allow list.

   Here is the list of IP addresses and domains that need to be added to your allow list.

   Refer to this support article to know more about how to fix issues with triggers.

Once the problem is resolved, modify the flow, save it, and then change it back and save again. The flow becomes aware that it's configuration changed, and tries to register its trigger again.

Verify connections

With the default settings, users only need to login to a connection once. They can then use that connection until it's revoked by an admin. A possible scenario is that the password for the connection can expire or there might be a policy in your organization which sets the connector’s login token expiration after a specific amount of time. Token lifetime policies have been configured on Azure Active Directory. For more information, check this Azure article or this support article.

To verify if your connections are broken:

1. Sign into Power Automate.

2. Go to Data > Connections.

3. Find the connection that's used in your flow.

4. Select Fix connections, and then update the credentials for your connection if there is a Fix connection message next to the Status column.

   

Verify if the flow uses a premium connector trigger

1. Edit your flow to find the connector name for the trigger.

2. Go to the list of connectors and search for that connector. If the connector is a premium connector, it shows below the name of the connector.

   

A standalone Power Apps or Power Automate license is required to access all premium, on-premises, and custom connectors. You can purchase new licenses at any time.

Check your license type

To view the type of license that you have:

• Go to My flows in navigation tab.
• Select any flow.
• In the Details section, find Plan. Your current license plan is listed.

Verify if trigger check is skipped

You just completed an event (for example, added a new list item or sent an email, etc.) that should have triggered the flow, but the flow didn’t run.

Go to My flows in the navigation pane, and then select the flow. In the 28-day run history, select All runs.

If you are expecting the flow to run but it didn’t run, see if it shows the trigger check was skipped at that time. If the trigger check was skipped, the trigger condition wasn’t met for the flow to trigger. Verify the inputs and trigger conditions of the flow to see you are using the latest configuration to trigger the flow.

Verify inputs and trigger conditions

Sometimes, the inputs and trigger conditions may cause failures. Follow these steps to verfiy your inputs and conditions.

1. Edit the flow.

2. Expand the first card to see what folders, sites, mailboxes, etc. are used in the trigger.

3. Select the ellipses (…) on the card

   

4. Select Settings.

   

5. Find Trigger conditions.

   If the field is empty, it means that there are no additional customizations and that the title of the card (in this case, when an item is created or modified) indicates when the trigger fires.

   If there are additional customizations in Trigger conditions, confirm that you are using the expected/correct inputs to trigger the flow.

   

Check permissions

Verify that you have access to the folders, sites, or mailboxes that are used in the trigger. For example, to be able to send email from a shared inbox via Power Automate, you need permissions to send an email via the shared inbox. Test sending an email from that shared mailbox in Outlook.

Verify if admin mode is turned on

If an environment’s admin mode is turned on, all background processes, including flows will be turned off, causing the flow to not trigger.

Follow these steps to disable the admin mode.

1. Go to the Power Platform admin center and sign in using Environment Admin or System Administrator role credentials.
2. From the left-side menu, select Environments, and then select a sandbox or production environment.
3. On the Details page, select Edit.
4. Under Administration mode, toggle Disabled to Enabled.
5. Optionally, you can set Background operations and Custom message, and then select Save.

If everything looks good but your flow is still not triggering, verify if your flow triggers after every step.

Try these steps:

1. Test the flow manually.
2. Remove, and then re-add the trigger.
3. Switch connection.
4. Turn off, and then turn on the flow.
5. Export, and then import the flow.
6. Create a copy of the flow.
7. If the trigger uses special conditions, like when an email arrives in specific folder, remove the folder, and then add it again.