Anyone else having coda pack issues? I came across 4 so far that all are timing out and giving me error messages.
I hope someone in the coda team is reading this and can look into it ASAP since most of my business is run in coda, and now it’s all not working properly :/.
Please help!
2 Likes
Yeah I’m getting gmail and twilio pack errors when sending via buttons
2 Likes
Ok - I had to sign in again to my accounts for each pack and its now working.
- Click the top right of the doc > Insert > Packs
- Find the pack in the list > Settings
- Then next to the private or shared account, click the 3 dots on the right > sign in again
Very frustrating, this seemed to have happened for no reason our end - but I hope this helps!
1 Like
Thank you! I’ll try that and see if it helps.
1 Like
Many don’t let you resign in, so even when I disconnect and reconnect, it’s touch and go. Something is definitely going on.
2 Likes
I’m also experiencing problems with my packs.
Error: 14 UNAVAILABLE: Received HTTP status code 429
1 Like
Also getting this error:
Error: 14 UNAVAILABLE: Received HTTP status code 429
Only getting it intermittently - Sometimes the pack works, sometimes not.
Likely related to the npm Supply Chain Attack (September 8, 2025).
What happened? A major supply chain attack compromised widely-used npm packages with over 2.6 billion weekly downloads after attackers hijacked a maintainer’s account through a phishing email. Your assessment is correct - this is a serious issue.
The attack began when developer Josh Junon (qix) fell victim to a phishing email from “support@npmjs.help” (a fake domain impersonating npm’s legitimate support) that tricked him into resetting his two-factor authentication.
Compromised Packages Include: Some of the most widely used packages: chalk (300 million weekly downloads), debug (358 million), and ansi-styles (371 million).
4 Likes
Wow. Tomorrow is not going to be fun.
2 Likes