Trigger is disabled – The flow trigger is disabled, preventing the flow from starting.

Power Automate flows rely on triggers to start execution. If a trigger is disabled, the flow cannot run. Users may encounter the following error:

“Trigger is disabled – The flow trigger is disabled, preventing the flow from starting.”

This issue occurs when the trigger is manually or automatically disabled, preventing the flow from executing as expected.

---

2. Causes of the “Trigger is Disabled” Issue

Several factors can cause a trigger to be disabled:

1. Manual Disabling – A user manually disabled the trigger or the entire flow.
2. Plan Limitations or Expiration – Some Power Automate plans restrict the use of premium triggers, and expired trials may disable them.
3. Microsoft Service Downtime or Outage – Power Automate or connected services may be experiencing an outage.
4. Environment or Tenant Policies – Organizational policies may prevent certain triggers from being used.
5. Throttling or Overuse – Exceeding API limits may cause Microsoft to disable the trigger.
6. Authentication or Permission Issues – If a trigger requires authentication and the credentials expire, it may be disabled.
7. Connector Issues – If a trigger relies on a third-party service (e.g., SharePoint, Outlook, or Teams), issues with that service may disable the trigger.
8. Trigger Conditions Not Met – If conditional logic prevents execution, the trigger may appear disabled.

---

3. Step-by-Step Troubleshooting Guide

Step 1: Check Flow Status and Enable the Trigger

1. Open Power Automate (https://flow.microsoft.com).
2. Go to My Flows and locate the affected flow.
3. If the flow is turned off, switch it ON.
4. Edit the flow and inspect the trigger. If it shows disabled, enable it manually.

Example of an enabled trigger:

Status: Enabled  
Trigger Type: Automated (e.g., "When an item is created in SharePoint")  

Example of a disabled trigger:

Status: Disabled  
Trigger Type: HTTP Request (Disabled due to plan limitations)  

---

Step 2: Verify Plan and Subscription Status

• Some premium connectors (e.g., HTTP triggers, SQL Server, Dataverse) require a Power Automate premium plan.
• If you are using a trial version, check if it has expired.

To check your plan:

1. Go to Power Automate > Settings > Billing & Licensing.
2. Ensure you have an active plan that supports your trigger.
3. If needed, upgrade to a premium plan.

---

Step 3: Check Microsoft Service Status

• If Microsoft services (e.g., Power Automate, SharePoint, Outlook, Teams) are experiencing downtime, triggers may be disabled.
• Visit https://status.office.com to check for outages.

---

Step 4: Verify Organizational Policies and Admin Restrictions

• Some organizations disable certain triggers (e.g., HTTP triggers, external APIs) for security reasons.
• To check this:
  1. Contact your Power Platform Administrator.
  2. Go to Power Platform Admin Center (https://admin.powerplatform.microsoft.com).
  3. Check if any DLP (Data Loss Prevention) policies restrict your trigger.

Example of an Allowed Trigger:

✔ SharePoint Trigger: Enabled  
✔ Outlook Trigger: Enabled  

Example of a Restricted Trigger:

❌ HTTP Request Trigger: Blocked by Admin  
❌ SQL Server Trigger: Restricted in this environment  

---

Step 5: Review API Limits and Throttling Issues

• If you exceed API call limits, Microsoft may disable your trigger temporarily.
• To check if throttling is causing the issue:
  1. Open Power Automate > My Flows.
  2. Select the affected flow and go to Run History.
  3. Look for messages like “429 Too Many Requests” or “Service limits exceeded”.

✅ Solution:

• Reduce the number of trigger executions.
• Use retry policies to handle API throttling.

Example of a retry policy in Power Automate:

1. Open the Trigger Settings.
2. Enable Retry Policy.
3. Set a retry interval (e.g., 5 retries, 1-minute delay).

---

Step 6: Re-Authenticate the Trigger if It Requires Login Credentials

• Some triggers (e.g., SharePoint, Outlook, SQL Server) require authentication.
• If the credentials expire, the trigger may be disabled.

To fix this:

1. Open Power Automate > My Flows.
2. Select the flow and go to Connections.
3. Check if any connections show “Authentication Failed”.
4. Click Fix Connection and re-enter credentials.

✅ Example of an Active Connection:

✔ SharePoint: Connected  
✔ Outlook: Connected  

❌ Example of a Disabled Connection:

❌ SharePoint: Authentication Failed (Reconnect Required)  
❌ Outlook: Token Expired  

---

Step 7: Check If the Trigger Conditions Are Preventing Execution

• Some triggers have conditions that must be met before they fire.
• If the conditions are too restrictive, the trigger may appear disabled.

To check this:

1. Open the flow in Edit Mode.
2. Click the trigger and expand Settings.
3. Check if any conditions are preventing execution.

✅ Example of a Working Condition:

Condition: "When a new file is added to SharePoint"  
✔ Condition: File Type = ".pdf" (Matches a valid file)

❌ Example of a Condition Blocking Execution:

Condition: "When a new file is added to SharePoint"  
❌ Condition: File Type = ".jpg" (No matching files)

✔ Solution:

• Modify or remove the condition to allow the trigger to fire.

---

Step 8: Delete and Recreate the Trigger

• If none of the above steps work, delete and recreate the trigger.

Steps to Recreate the Trigger:

1. Open the flow in Edit Mode.
2. Click Delete Trigger.
3. Click + Add Trigger and select the appropriate one.
4. Configure it again and save the flow.

---

4. Preventative Measures

To avoid “Trigger is Disabled” issues in the future:

✔ Monitor Flow Status – Regularly check if triggers are enabled.
✔ Keep Credentials Updated – Ensure authentication tokens do not expire.
✔ Understand Plan Limitations – Upgrade if necessary.
✔ Check for API Throttling – Reduce high-frequency triggers.
✔ Stay Aware of Admin Policies – Ensure your environment allows the trigger.