Power Automate SharePoint Trigger Intermittently Stops Firing with No Run History

For this symptom pattern—no run history at all, flow still enabled, item is created successfully, and the stop is intermittent—the most relevant checks are the trigger path itself, skipped trigger checks, suspension/policy issues, and trigger registration failures.

1. Confirm whether the trigger check is being skipped
   • In Power Automate, go to My flows > select the affected flow.
   • In 28-day run history, select All runs.
   • If the expected event time shows a skipped trigger check, the trigger condition was not met, so the flow was never initiated.
   • Then open the flow in Edit, select the trigger card, and review Settings > Trigger conditions.
   • If a trigger condition exists, temporarily remove it and test again. If the flow starts working, the condition is filtering out the events.
2. Check whether the flow is suspended or blocked by DLP policy
   • A data loss prevention (DLP) policy can suspend a flow, which prevents the trigger from firing.
   • Open the flow, try Edit and Save.
   • If the flow checker reports a DLP violation, the flow is being blocked by policy and an administrator must update or remove the blocking policy.
3. Check for trigger registration failure
   • On the flow Details page, look for:
     • There’s a problem with the flow’s trigger. Fix the trigger.
   • If that banner appears, select Fix the trigger, then select the failed trigger to inspect the underlying error.
   • Common user-fixable causes include:
     • expired or changed connection credentials
     • invalid trigger input
     • webhook registration failure
   • If the failure is related to network allowlisting, Power Automate service endpoints might not be in the organization allowlist. In that case, IT must add the required IP addresses and domains.
   • After the issue is corrected, modify the flow and save it, then save again if needed so Power Automate retries trigger registration.
4. Verify connection health even if the flow is enabled
   • Trigger failures with 4xx status codes are typically caused by issues that must be fixed in the flow or connection, such as a changed connection or expired password.
   • Since the flow worked previously and then stopped without edits, a connection/authentication issue is a strong match for this behavior.
5. Account for polling behavior
   • Event-based triggers in Power Automate are not real-time push notifications. They use polling intervals, typically 1–5 minutes depending on the connector.
   • Since more than 5–10 minutes was already tested, normal polling delay is less likely to explain the full issue, but it still confirms that “no immediate run” alone is not enough to indicate failure.
6. Check for service-side communication problems
   • A communication problem, service outage, policy change, or password expiry can delay or prevent trigger reaction.
   • Review Help + support in the Power Platform admin experience for active outages.
   • Clearing the browser cache is also listed as a troubleshooting step, although that is more relevant to portal behavior than SharePoint event delivery.
7. Interpret the separate test flow result carefully
   • The fact that a simple When an item is created > Send an email flow works against the same list suggests the SharePoint list itself is not broadly failing.
   • That points more strongly to something specific in the affected flow, such as:
     • trigger conditions
     • trigger registration state
     • connection state
     • suspension/DLP impact on that flow only
8. If the banner remains after recovery
   • A known issue exists where the trigger problem banner can continue to display even after later trigger events succeed.
   • If runs resume successfully, the lingering banner alone does not prove the trigger is still broken.

Based on the described behavior, the highest-value next steps are:

1. check All runs for skipped checks,
2. review and temporarily remove Trigger conditions,
3. inspect the flow Details page for the Fix the trigger banner,
4. open the trigger error details if present,
5. Edit and Save the flow to force trigger re-registration,
6. verify the flow is not suspended by DLP or a connection/authentication problem.

References:

• Troubleshoot cloud flow errors
• Troubleshoot Power Automate trigger problems and errors
• "There is a problem with the flow's trigger" error shown in a flow's run history
• Troubleshoot common issues with triggers