Vercel CLI Error: Too many requests

Hi,

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?

Github action script:

# First Step - No errors
vercel pull --yes --environment=${{ env.VERCEL_ENVIRONMENT }} --token=$DEPLOYER_TOKEN --scope=[REDACTED]

# Second Step - Builds without errors
vercel build --token=$DEPLOYER_TOKEN --scope=[REDACTED]

# Third Step - Throws Error 
echo "🚀 Deploying PR as: [REDACTED]"
url="$(vercel deploy --prebuilt --target ${VERCEL_ENVIRONMENT} --token=$DEPLOYER_TOKEN --scope=[REDACTED])"
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.
3 Likes

I have the exact same issue, and can no longer deploy to prod using my current CI/CD. Help needed urgently!

2 Likes

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,

2 Likes

Pinning the version to 43.3.0 worked for me :+1:

Thanks! We are working on a fix.

1 Like

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.

2 Likes

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.

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.

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:

name: PR Preview Deployment
env:
  VERCEL_ORG_ID: ${{ secrets.VERCEL_ORG_ID }}
  VERCEL_PROJECT_ID: ${{ secrets.VERCEL_PROJECT_ID }}
  VERCEL_ENVIRONMENT: preview
  # Custom domain for PR previews
  URL: [REDACTED]

on:
  pull_request:
    types: [opened, synchronize, reopened]

jobs:
  Deploy-Preview:
    runs-on: ubuntu-latest
    environment: Preview
    steps:
      - uses: actions/checkout@v3
      
      - name: Determine deployer token
        id: token
        run: |
          # For PRs, use the PR author instead of the actor
          USER="${{ github.event.pull_request.user.login }}"
          chmod +x .github/scripts/get-deployer-token.sh
          eval $(.github/scripts/get-deployer-token.sh "$USER")
          echo "token_name=$token_name" >> $GITHUB_OUTPUT
          echo "deployer_name=$deployer_name" >> $GITHUB_OUTPUT
          
      - name: Install Vercel CLI
        run: npm install -g vercel@43.3.0 corepack && corepack enable
        # See: https://community.vercel.com/t/vercel-cli-error-too-many-requests/14173
        # run: npm install -g vercel@latest corepack && corepack enable
        
      - name: Pull Vercel Environment Information
        env:
          DEPLOYER_TOKEN: ${{ secrets[steps.token.outputs.token_name] }}
        run: vercel pull --yes --environment=${{ env.VERCEL_ENVIRONMENT }} --token=$DEPLOYER_TOKEN --scope=[REDACTED]
        
      - name: Build Project
        env:
          DEPLOYER_TOKEN: ${{ secrets[steps.token.outputs.token_name] }}
          APP_DESTINATION: [REDACTED]
          WORDPRESS_DESTINATION: [REDACTED]
          BUILD_NEXUS_API_URL: [REDACTED]
          BUILD_VILLA_NEXT_NEXUS_API_KEY: [REDACTED]
        run: vercel build --token=$DEPLOYER_TOKEN --scope=[REDACTED]
        
      - name: Deploy Project
        env:
          DEPLOYER_TOKEN: ${{ secrets[steps.token.outputs.token_name] }}
        run: |
          echo "🚀 Deploying PR as: ${{ steps.token.outputs.deployer_name }}"
          url="$(vercel deploy --prebuilt --target ${VERCEL_ENVIRONMENT} --token=$DEPLOYER_TOKEN --scope=[REDACTED])"
          vercel alias --token=$DEPLOYER_TOKEN --scope=[REDACTED] "$url" ${{ env.URL }}
1 Like

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?

Thanks. We are investigating this

@swarnava 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.

Hi @ad-villahomes , 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 @swarnava

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
2025-06-25T18:20:32.179Z  Build machine configuration: 4 cores, 8 GB
2025-06-25T18:20:32.195Z  Retrieving list of deployment files...
2025-06-25T18:20:32.457Z  Previous build caches not available
2025-06-25T18:20:32.723Z  Downloading 2906 deployment files...
2025-06-25T18:20:45.538Z  Using prebuilt build artifacts...
2025-06-25T18:20:45.895Z  Deploying outputs...
To deploy to production ([REDACTED] +1), run `vercel --prod`
Vercel CLI 44.2.4
> Assigning alias[REDACTED] to deployment [REDACTED]
Fetching domain [REDACTED] under [REDACTED]
Creating alias
> Success! [REDACTED] now points to [REDACTED] [1s]

Awesone, thanks for confirming!

I am still seeing this issues with vercel@44.2.5

Vercel CLI 44.2.5
Retrieving project…
Deploying ***/***
Uploading [--------------------] (0.0B/27.4MB)
Uploading [=====---------------] (6.9MB/27.4MB)
Uploading [==========----------] (13.7MB/27.4MB)
Uploading [===============-----] (20.6MB/27.4MB)
Uploading [====================] (27.4MB/27.4MB)
Error: Too many requests - try again in 23 seconds (more than 300, code: "api-projects-get"). (429)

Hi @chrizzly,

Can you share --debug output? Just append -debug in your existing deploy command which should produce more verbose logs.