My Google API is not stable

[joffreypersia]

Hi,

In my workflow, I am working on Google API to clone google doc, replace strings, export pdf and send email with the pdf.

Globally it works.
But sometimes, I get :
The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client. (item 0)

I don’t get it, the credentials are good, the connexion is OK
But it break after few days or few iterations. Usually, it never breaks at the same node. Sometimes it is the Doc, the mail or the drive.
if I go to credential and connect again it works until a probably next break.

Is there any good tutoriel how to set up a proper Google App API so it is stable ?
Should it be caused by the fact that the Google App is in test mode, and not in prod ?

I am using n8n cloud service, up to date with the last stable version.
n8n version : 1.63.4
n8n cloud plan : starter

Thank you

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[giulioandreini]

Hi @joffreypersia
and welcome back to the n8n community

This can happen if the publishing status of your project on the Google Cloud Console is set to “testing”. The Google docs say:

Authorizations by a test user will expire seven days from the time of consent. If your OAuth client requests an offline access type and receives a refresh token, that token will also expire.

(Link)

In the “OAuth consent screen” page (on the Google Cloud Console) check that Publishing status is set to “In production”

Let me know if this helps