On my self-hosted n8n I am using some Microsoft and Google nodes, these nodes for sure need some credentials to be set through auth2. After some time workflows fail because of these credentials and I always need to go again to the credentials and reactivate them be logging in or connect again as shown
Hey @nader95
To fix this issue permanently, just follow these two simple steps:
Step 1 Update your Google Console settings
Go to your Google Cloud Console and change your OAuth app status from Testing to Production. This is where you got your Client ID and Secret from.
Step 2 Reconnect your account once
After that, go back to your workflow and reconnect your Google account one more time.
That’s it! Once done, your workflow will stay connected and won’t keep disconnecting or failing anymore.
Great! Thank you so much let me try. Will it be the same for microsoft? @moosa
@nader95 you can check it on if there is similar setting. Most probably there will be something like than too.
Glad this got solved. Extra tip for folks landing here from search: the Google “Testing → Production” flip also clears the 7-day refresh-token expiry that catches a lot of people off-guard — tokens issued under Testing get force-revoked after a week even if everything else is configured correctly.
If you’re juggling many OAuth creds across self-hosted tools, centralizing refresh outside n8n is worth it (open-source gateway we’ve been building: github.com/ChronoAIProject/NyxID). For single-instance setups, the Production-mode flip is usually enough.
