The “Connection is lost” error in Power Automate occurs when a flow loses access to its data source or external service. This can happen due to expired authentication tokens, permission changes, API limits, or network issues.
This guide provides step-by-step troubleshooting to resolve connection issues and prevent future disruptions.
Step 1: Check and Reauthenticate Connections
1. Verify Connection Status in Power Automate
- Go to Power Automate → Click on Data → Select Connections.
- Look for any connections labeled “Needs attention” or “Invalid”.
- If a connection is broken, click “Fix connection” and re-authenticate.
2. Refresh or Re-add the Connection
- If re-authentication does not work, try removing and re-adding the connection.
- Click “New connection”, select the service, and sign in again.
- Update all flows that rely on the old connection with the new one.
Step 2: Verify Permissions & Access
1. Ensure You Have the Correct Permissions
- Some services (e.g., SharePoint, Dataverse, SQL) require specific access levels.
- Verify that your account has the correct read/write permissions to access the data source.
- If the service uses OAuth authentication, check if the token has expired.
2. Check for Organizational Restrictions
- Some organizations block third-party app connections for security reasons.
- Ask your IT administrator if there are conditional access policies affecting Power Automate.
Step 3: Check Service Status & API Limits
1. Verify If the Service is Down
- If the connection is lost to Microsoft 365, SharePoint, or other cloud services, check:
- For third-party services (e.g., Google Drive, Salesforce), visit their status page.
2. API Rate Limits and Quotas
- Some services limit the number of requests per minute/hour.
- If you receive a 429 (Too Many Requests) error, try:
✅ Adding a Delay action between requests.
✅ Reducing the frequency of the flow.
✅ Switching to a premium connector for higher limits.
Step 4: Check Network & Firewall Settings
- If using on-premises data sources (SQL, file shares), ensure:
✅ The On-premises Data Gateway is running and updated.
✅ The network firewall allows Power Automate traffic.
✅ Your VPN or proxy is not blocking the connection.
Step 5: Recreate or Reconfigure the Flow
1. Test the Flow with a New Connection
- Duplicate the flow and change the trigger or action to use a fresh connection.
2. Replace Failing Actions
- Some actions may become outdated or incompatible.
- Try using an alternative action or API call if possible.
Step 6: Enable Error Handling & Notifications
- Use “Configure Run After” settings to handle failed connections gracefully.
- Add a Scope action to group dependent actions and catch errors.
- Set up email or Teams notifications when a connection is lost.
Conclusion
The “Connection is lost” error in Power Automate is often due to expired authentication, permission changes, API limits, or service downtime. By reauthenticating, verifying permissions, checking service status, and ensuring network stability, you can restore the connection and prevent future issues.