I seem to be running into the above issue when trying to authorize through OAuth2 API. Happens on both client credentials+refresh and authorization code type credentials.
Often will occur after a node has been running successfully for some time.
Restarting the workspace seems to resolve it only for a brief period.
Please provide more details about:
To share your workflow you can copy and paste it inside a code block.
To create a code block you just have to click here:
Your workflow will show up like this:
Hey Solomon,
Currently it occurs on OAuth2 across client+refresh and authorisation code credential types. The problem seems momentarily resolved after restarting the workspace or updating to a new version of n8n but seems to reoccur after some usage. Currently running version 1.84.1 on Cloud.
Hi, just a follow up that this seems to momentarily resolve when I restart the workspace. Currently using client and refresh type credentials for the OAuth set up. Could n8 be storing an old access token somewhere that it only deletes when I restart the workspace?