The 'Invalid connection — please reauthorize app' error in Make means the stored credentials for a connected service have expired or been revoked. Make auto-deactivates the scenario when this happens. Open the connection in the scenario editor, click Reauthorize, and re-authenticate with the service. For API-key connections, generate a fresh key and update the connection.
What does "Invalid connection — please reauthorize app" mean in Make?
When Make shows this error, it has classified it as an AccountValidationError — one of Make's 13+ formal error types. The credentials stored for a connected service (OAuth token, API key, or access token) are no longer valid. Make cannot authenticate with the third-party service and the scenario stops processing.
Make automatically deactivates scenarios that encounter AccountValidationError. This is different from temporary ConnectionErrors (HTTP 502/503/504) where Make retries automatically. An AccountValidationError requires manual intervention — you must reauthorize the connection before the scenario can run again.
This error type is particularly impactful because it is one of only two error types (along with OperationsLimitExceededError) that immediately disable scenario scheduling. A single expired credential can shut down an entire automation pipeline.
Common causes
The OAuth access token expired
and Make's automatic refresh failed because the refresh token was also expired or revoked
The user changed their password
on the connected service, invalidating all OAuth sessions
The API key or access token was rotated or
regenerated on the service's dashboard without updating Make
The connected service's administrator revoked Make's application access in
their security or integration settings
Two-factor authentication was enabled or
changed on the connected service account
The connected service changed its API version or
OAuth scopes, requiring re-authorization with new permissions
How to fix "Invalid connection — please reauthorize app" in Make
Open the scenario that is failing. Click on the module showing the error. You will see the connection with an error indicator. Click on the connection name to open the connection editor, then click 'Reauthorize.'
For OAuth connections (Google, Slack, HubSpot, etc.): a browser popup opens where you log into the service and grant Make access again. Verify you are authorizing with the correct account.
For API-key connections: go to the service's developer or API settings, verify the key is still active, or generate a new one. Copy the new key into Make's connection settings.
After reauthorizing, click 'OK' to save, then run the scenario manually to confirm it works. Check all other scenarios using the same connection — they will all fail with the same error until the connection is refreshed.
To prevent future disruptions, set up Make's error notification system. Go to Scenario Settings > Notifications and configure email or webhook alerts for errors. You can also use Make's Break error handler directive to pause execution and queue data during authentication failures, then replay it after the connection is fixed.
Prevention tips
- After reauthorizing one connection, check all scenarios using the same connection — Make shares connections across scenarios
- Use the Break error handler directive on critical modules to queue data during authentication failures, allowing you to replay it after fixing the connection
- Set up scenario error notifications (email or webhook) to be alerted immediately when AccountValidationError occurs
- For services with short-lived tokens, consider scheduling a regular test scenario that verifies the connection is still active
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
My Make scenario shows 'Invalid connection — please reauthorize app' for a Google Sheets module. I've reauthorized but it keeps happening every few weeks. How do I set up Make to handle this gracefully?
My Make (Integromat) scenario has an AccountValidationError on the [module name] module. Walk me through reauthorizing the connection and setting up error handlers to prevent data loss when this happens.
Frequently asked questions
Why does Make show "Invalid connection — please reauthorize app"?
The stored credentials for a connected service expired or were revoked. This is classified as an AccountValidationError in Make's error system. Common triggers include expired OAuth tokens, password changes, API key rotations, and admin access revocations.
Does Make automatically disable scenarios with connection errors?
Yes. AccountValidationError immediately disables scenario scheduling. This is different from temporary ConnectionErrors where Make retries automatically. You must manually reauthorize the connection and re-enable the scenario.
How do I reauthorize a connection in Make?
Open the failing scenario, click the module with the error, click the connection name, and click 'Reauthorize.' For OAuth, re-authenticate in the browser popup. For API keys, enter the new key. Save and test the scenario.
Will I lose data when Make disables a scenario due to authentication failure?
Data that was not yet processed will not be lost — it remains in the source system. However, without the Break error handler, Make may skip events that occurred during the downtime. Use the Break directive to queue data during failures.
Can RapidDev help build resilient Make scenarios that handle connection failures?
Yes. RapidDev can design Make scenarios with proper error handler directives (Break, Resume, Rollback), set up monitoring for connection health, and implement retry strategies that prevent data loss during authentication failures.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your issue.
Book a free consultation