https://linen.dev logo
Urgent: 401 Retrieval Errors Using Google Tokens f...
# 🖥│support-forum
c
Hi there, overnight last night (MST) our gmail connections began returning 401 errors when used for direct gmail API retrieval operations Is there any known issues with connection status or token rotation issues? The issue appears scoped to gmail auth config and in our case is returning 401 on message GET requests Here is an example connected account you can use experiencing the issue ca_I35ML5cnTeJw Triggers continue to send without issue it appears @project_id: Us8LGifAQRr- @org_id: tWzQRbwirxi- @org_member_email: chad@pingassistant.com @user_id: 36fa1401-3927-43eb-9c94-677357ead525
When it started 2026-04-22T08:15:33 UTC (~6h45m ago, still ongoing as of 14:59 UTC). No gap/recovery — errors have been continuous since.
This is incredibly frustrating and the second time we have been rug pulled with no advanced notice This is a complete anti-pattern for an SDK/API provider @Uday @Lingala @Abhishek
I have to go dig through doc PRs for a breaking change announcement
and now I have no path for remediation
u
Hey @Chad Holmes, really sorry for the inconvenience. This is a recent change from our end. I understand the affect of this change on your flow but It was a necessary security change to prevent credential outages for every user using Composio's default credentials. Due to the high risk factor, we had to release this change. I've DM'ed you with additional details, could you please check?
c
Checking
I understand a security change. But it needs to be broadcasted and notified as a breaking change. I spent 1 hour finding the root cause when I could have saved all that time working towards a migration on our end that could solve the problem
Happy to follow up via DM
5 Views