The “Invalid Connection” error in Power Automate occurs when a flow is using an expired or broken connection. This prevents actions from retrieving or sending data, causing the flow to fail.
Error Message:
"Invalid connection – The connection used in the flow is invalid or expired."
This issue can be caused by:
- Expired or revoked authentication credentials
- Changes in permissions or roles
- Incorrect connection settings
- Service outages affecting the connector
2. Common Causes and Fixes
Cause | Description | Fix |
---|---|---|
Expired Authentication Token | OAuth tokens expire and need reauthentication. | Refresh or reauthenticate the connection. |
Revoked or Changed Credentials | Passwords have changed or access has been revoked. | Update the credentials and reconnect. |
Insufficient Permissions | The user no longer has access to the service. | Grant the required permissions. |
Service Outage or API Restriction | The connected service is down or has exceeded limits. | Check service status and API quotas. |
Connector Configuration Error | The connection settings (e.g., URL, environment) are incorrect. | Verify and update connection settings. |
3. Step-by-Step Troubleshooting Guide
Step 1: Check the Connection Status
- Open Power Automate (https://flow.microsoft.com).
- Click on Data → Connections from the left menu.
- Find the connection linked to the flow.
- If the connection shows Needs Attention or Invalid, click Fix Connection and reauthenticate.
Example Fix:
- If the connection to SharePoint, SQL Server, or Dataverse has expired, sign in again.
- If using OAuth authentication, refresh the token.
Step 2: Reauthenticate the Connection
- Click Fix Connection next to the affected connection.
- Sign in using the correct credentials.
- Click Save and Test the flow.
Example:
- If a SharePoint connection fails, re-enter Microsoft 365 credentials.
- If using a third-party API, ensure the API key or OAuth token is valid.
Step 3: Verify User Permissions
Some data sources require specific permissions to access data.
Check for permission changes:
- Has the user been removed from a SharePoint site?
- Has an admin revoked access to a SQL Server database?
- Has a role been changed in Dataverse or Power BI?
Example Fix:
- For SharePoint, ensure you have at least Edit permissions.
- For SQL Server, ask the database administrator to grant access.
Step 4: Check for Service Outages
If the data source is experiencing downtime, your connection may fail.
How to check service status:
- Microsoft Services: https://status.office365.com
- Azure Services: https://status.azure.com
- Third-party APIs: Check the provider’s status page.
Example Fix:
- If the service is down, wait for it to be restored.
- If API limits are exceeded, reduce API calls or wait for the quota to reset.
Step 5: Verify Connector and Environment Settings
If the connection settings are incorrect, the flow will fail.
Check for errors like:
- Wrong SharePoint site URL
- Incorrect SQL Server database name
- Mismatched Dataverse environment
Example Fix:
- Open Power Automate and edit the affected flow.
- Click on the failing action.
- Verify that the URL, credentials, and settings are correct.
Step 6: Recreate the Connection
If the connection remains invalid, delete and recreate it.
Steps to recreate the connection:
- Go to Power Automate → Data → Connections.
- Find the affected connection.
- Click Delete and then + New Connection.
- Re-add the connection with updated credentials.
Example Fix:
- If an SQL Server connection is invalid, remove it and re-add it.
- If using OAuth authentication, ensure the token is refreshed.
Step 7: Test the Flow After Changes
- Click Save in Power Automate.
- Run a Test with sample data.
- If the error persists, check Run History for logs.
If the issue is resolved, ensure all users have updated access.