Troubleshoot common issues with triggers

Here are a few tips and tricks for troubleshooting issues with triggers.

Identify specific flow run

Sometimes, you might need to Identify specific flow runs to troubleshoot your flows.

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's 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 violates a DLP policy. Your admin can change the DLP policy.

2. The trigger may be failing. Follow these steps to confirm:

   1. Sign in to Power Automate.

   2. Go to My flows, and then select your flow.

   3. 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 this failure is that the Power Automate service endpoints are not part of the allow list. To fix it, confirm that your IT department has added these endpoints 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 learn more about how to fix issues with triggers.

After the problem is resolved, modify the flow and then save it. You can then change it back to its original state, and then save it again. The flow becomes aware that its configuration changed, and it tries to register its trigger again.

Verify connections

With the default settings, users only need to sign in 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 authentication token to expire after a specific amount of time. Token lifetime policies are configured on Microsoft Entra ID. For more information, review this Azure article or this support article.

Follow these steps to verify if your connections are broken:

1. Sign in to Power Automate.

2. Go to Data > Connections.

3. Find the connection that your flow uses.

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 then search for that connector. If the connector is a premium connector, PREMIUM displays 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 licenses at any time.

Check your license type

Follow these steps to view the type of license that you have:

1. Sign in to Power Automate.
2. Go to My flows in the left pane.
3. Select any flow.
4. 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, you added a new list item or sent an email that should have triggered the flow, but the flow didn’t run.

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

If you expect 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, it means that the trigger condition wasn’t met for the flow to trigger. Verify the flow the inputs and trigger conditions to confirm if 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 verify your inputs and conditions.

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. Send a test 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 with 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, set the slider to Disabled.

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 the 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 a specific folder, remove the folder, and then add it again.

My trigger is firing for old events

There are two types of triggers—polling triggers and Webhook triggers.

If you turned off your flow and then turned it back on, depending on your trigger type, your old triggers may be processed.

A polling trigger periodically makes a call to your service to look for new data, whereas a Webhook trigger responds to a push of new data from the service.

See the following table to understand how your flow responds when it's turned back on.

Follow these steps to determine the type of trigger that your flow uses.

My flow is triggered multiple times or some of my actions run multiple times

You may encounter a scenario where a single flow run has some (or all) of its actions duplicated. While the UI doesn't show this problem, you might see the results of the flow being duplicated. For example, duplicate emails sent, or duplicate list items created.

One of the reasons this might happen is because of the "at-least-once" design of Azure Logic Apps.

Most of the times, this indicates that there was an issue with the Azure service. Usually, these issues are self-healed quickly. To ensure that your flows don't create duplication, ensure you design them to be idempotent—which is to say that the flow needs to account for the possibility of duplicate inputs.

An example of idempotency would be checking to see if a duplicate SharePoint document already exists before trying to create it, or using key constraints in Dataverse to prevent duplicate records getting created.

Another possibility is for flow triggering multiple times might be having copies of the flow active in different environments that are triggering based on same condition. Use trigger conditions to customize triggers to reduce the number of times it triggers.

My recurrence trigger runs ahead of schedule

Confirm that you've set the Start time on the Recurrence card to ensure it runs only at the time that you need. For example, set Start time to '2022-10-10T10:00:00Z' to start your trigger at 10:00 AM.

There's a delay before my trigger fires

If the trigger is a polling trigger, it wakes up periodically to check if any new events have occurred.  The wake-up time depends on the license plan on which the flow runs.

For example, your flows may run every 15 minutes if you’re on the Free license plan. On the Free plan, if a cloud flow is triggered less than 15 minutes after its last run, it’s queued until 15 minutes have elapsed.

And, if your license is the Flow for Office 365 plan (from your Enterprise license E3, E5, etc.) or the Flow for Dynamics 365 plan, your flow won't run again until five minutes have elapsed. So, it may be a few minutes between the time the triggering event occurs and the time the flow begins.

Follow these steps to check the trigger wake up frequency.

If it's taking much longer than expected for your flow to trigger, here are the two likeliest reasons:

1. There's been too many calls to the connector or flow, causing it to be throttled. To verify if your flow is being throttled, manually test the flow to see if it triggers immediately. If it triggers immediately, it is not throttled.

   You can check the Power Automate analytics to learn more about your flows.

   If your flow is frequently throttled, redesign your flow to use fewer actions. Learn more about plan limits and tips to optimize flows to use fewer actions.

   Additional tips:

   1. Acquire a Power Automate Premium (previously Power Automate per user) or Power Automate Process license (previously Power Automate per flow). After this is acquired, open and then save the flow, in order to refresh the entitlement associated with it, and to change the throttling mode.

   2. Split the flow into several instances. If the flow processes data, you can divide this data into subsets (per country/region, per business area, etc.).

   3. After this, you can use Save As on the flow to create several instances that will process their own data. Since the quota is per flow, this can be used as a workaround.

2. There was a communication issue that prevents Power Automate from reacting to trigger events. Potentially, because of a service outage, policy change, password expiry, and so on, that caused the delay. You can view Help + support to find out if there are any active outages. You can also clear the cache of the browser and then retry.

Power Apps trigger issues

Unable to rename actions in a cloud flow – This is a known issue for flows that use Power Apps triggers. As a workaround to rename actions, remove the trigger. Rename the actions, add your Power Apps trigger, and then configure variables wherever needed.

After an app is published, make copies of the flows used by that app to make any updates. Any update to a cloud flow that's referenced by a published app can break existing users. Do not delete or turn off existing flows until all users have been upgraded to the new published version of the app.

SharePoint trigger issues

SharePoint triggers, for example When a file is created or modified, will not fire if a file is added or updated in a subfolder. If you need the flow to trigger on subfolders, create multiple flows.

Users are unable to run flows that are shared with them, but the owner can run the flow

You can try one of the following:

1. Fix or update connections.

   If your flow uses a Manual trigger, it needs the connection of the user who is triggering the flow. If it uses the Recurrence trigger, it can run on the flow maker's connections.

2. Confirm the user has the appropriate license for the connections in the flow.

   A Power Automate license is required for the user to perform any actions like save, turn off, and more. A Power Apps, Dynamics 365, or Microsoft 365 license is not sufficient. Users with whom flows that use premium connectors are shared will each need a Power Automate Premium (previously Power Automate per user) or Power Automate Process license (previously Power Automate per flow) license to edit or manually trigger the flow. If the user was previously able to save or modify the flow, it's possible that their license has expired.

   Alternatively, you can start a trial for the Per User plan for 90 days, after which you will need a paid plan to run or edit flows that use premium connectors. See the licensing page or this support article for more details.

My flows don't trigger after I change the environment URL

To resolve this issue, edit each flow and save it. The triggers should start firing again.