I've been using Github Actions to build my NextJS application for Vercel for some time. Today, when I added some SSG pages, I started to get this error. Any ideas on how I can increase the limit?
vercel alias --token=$DEPLOYER_TOKEN --scope=[REDACTED] "$url" [REDACTED]
Output:
[ ... vercel build logs ...]
🚀 Deploying PR as: [REDACTED]
Vercel CLI 44.2.1
Retrieving project…
Deploying [REDACTED]
Uploading [--------------------] (0.0B/19.4MB)
Uploading [=====---------------] (4.8MB/19.4MB)
Uploading [==========----------] (9.7MB/19.4MB)
Uploading [===============-----] (14.5MB/19.4MB)
Uploading [====================] (19.4MB/19.4MB)
Error: Too many requests - try again in 29 seconds (more than 400, code: "api-projects-list"). (429)
Error: Process completed with exit code 1.
I have the exact same issue, and can no longer deploy to prod using my current CI/CD. Help needed urgently!
Vercel Staff
Hi there,
Could you try installing vercel@43.3.0 and let us know if you are still experiencing this issue? You might need to tweak the CLI version in install step with npm i vercel@43.3.0 or similar,
Pinning the version to 43.3.0 worked for me
Vercel Staff
Thanks! We are working on a fix.
Vercel Staff
We have just released vercel@44.2.3 which should fix the issue. This means you can use npm i vercel@latest again to setup your CI workflow.
vercel@44.2.3 is not working for me:
🚀 Deploying PR as: [REDACTED]
Vercel CLI 44.2.3
Retrieving project…
Deploying [REDACTED]
Uploading [--------------------] (0.0B/19.8MB)
Uploading [=====---------------] (5.0MB/19.8MB)
Uploading [==========----------] (9.9MB/19.8MB)
Uploading [===============-----] (14.9MB/19.8MB)
Uploading [====================] (19.8MB/19.8MB)
Error: Too many requests - try again in 5 seconds (more than 400, code: "api-projects-list"). (429)
Error: Process completed with exit code 1.
Vercel Staff
Hi Andrew,
Thank you for your reply. You can use 'vercel@43.3.0' while we investigate this. I have escalated this again internally.
Thanks, Swarnava.
vercel@43.3.0 works for us, a deploy completed successfully just now.
Vercel Staff
Thanks for confirming. Do you use the CLI anywhere else? Other app workflows? Or just a single CI workflow to trigger builds?
This Github Action workflow is the only place we use Vercel CLI. Included below is the action .yaml file for your reference:
vercel alias --token=$DEPLOYER_TOKEN --scope=[REDACTED] "$url" ${{ env.URL }}
I'm having the same issue
This comment is not helpful. Did you read this thread? What version of vercel is failing? Did you try pinning vercel@43.3.0?
reply to #12
Vercel Staff
Thanks. We are investigating this
unfortunately adding a --debug flag to the vercel alias command above on the last line of the .yaml does not add any additional output. Let me know if there is anything I can help with.
Vercel Staff
Hi , we have released vercel@44.2.4 which removes the code we believe caused the bug.. Could you try using vercel@latest and let us know how it goes?
Hi
vercel@44.2.4 appears to be working:
Run echo "🚀 Deploying PR as: [REDACTED]"
🚀 Deploying PR as: [REDACTED]
Vercel CLI 44.2.4
Retrieving project…
Deploying [REDACTED]
Uploading [--------------------] (0.0B/13.2MB)
Uploading [=====---------------] (3.3MB/13.2MB)
Uploading [==========----------] (6.6MB/13.2MB)
Uploading [===============-----] (9.9MB/13.2MB)
Uploading [====================] (13.2MB/13.2MB)
Inspect: [REDACTED] [6s]
Preview: [REDACTED] [6s]
Queued
2025-06-25T18:20:32.179Z Running build in Washington, D.C., USA (East) – iad1
