Hi @CU13030535-0,
A few users have recently reported similar behavior where flows suddenly stop working even though nothing in the flow was changed. In some cases this happens after backend updates to connectors or service endpoints, which can cause flows that previously worked to start failing or not triggering correctly.
Before making changes to the flow logic, it may help to check a few things first:
1. Check Power Platform service health
Sometimes these issues are related to temporary service problems. You can check the Microsoft 365 service health dashboard or the Power Platform admin center to see if there are any ongoing incidents affecting Power Automate or the connector used in your flow.
2. Review the run history
Open the flow → Run history and expand the failed run (or last successful run).
Look for:
This usually gives more detail about where the failure occurs.
3. Re-authenticate the connections
If the flow uses connectors such as SharePoint, Outlook, OneDrive, etc., try opening the flow connections and re-signing the connection. Backend changes or token expiration can sometimes cause flows to stop working until the connection is refreshed.
4. Save the flow again
A simple edit + save can sometimes re-register the trigger with the Power Automate service.
If the issue started suddenly and multiple flows are affected at the same time, it may indicate a temporary platform or connector issue, so checking the service health or testing again later can also help confirm whether it is environmental.
If possible, sharing the exact error message or a screenshot of the failed run step would help the community narrow down the root cause.
Hope this helps.
