API Deployment Access Keeps Disconnecting My Credentials

I’m using the Pickaxe Community Nodes in n8n.

I got this bright idea thinking I could replace all of my AI nodes in n8n with my pickaxe API instead…

But after doing that a lot of my Pickaxe nodes stop being authorized within 2-5 days. I authorize them with OAuth2 again and again. They work for a few days REALLY well and I’m VERY happy with them. But they keep saying expired access token afterwards until I go in and authorize it again.

Does anyone have a way to stay permanently authorized? Was this done intentionally? Is this a bug? Is there a different setting that I’m not aware of and should be using instead? @danny_support I’d appreciate your support if you’re able to help a brother out!

Hi @enochleffingwell ,

Thank you for flagging this.

I’ll test this on my side and pass the details along to our engineering team to help with their investigation.

1 Like

Thank you. I appreciate you looking into this. I really like the community node a lot. But this morning I did find out if I go back to using custom HTTP requests. Then I don’t think they’re going to time out because they used to be more stable in the past.