How to fix Cloud Functions: HTTP 429 - Quota exceeded when deploying functions in Firebase

FirebaseINTERMEDIATEMEDIUMUpdated Dec 22, 2025· 150 views

This HTTP 429 error occurs when you exceed Firebase's API rate limits while deploying Cloud Functions, typically when deploying many functions simultaneously or in rapid succession through CI/CD pipelines.

Quick fix

Fixes 429

# Wait before retrying
sleep 120
firebase deploy --only functions
  1. Wait for quota reset
  2. Deploy functions in small batches
  3. Implement sequential deployment script
  4. Configure CI/CD pipeline for rate limiting
firebase — error
# Wait before retrying
sleep 120
firebase deploy --only functions
Cloud Functions: HTTP 429 - Quota exceeded when deploying functions

What this error means

This error indicates that your Firebase project has exceeded the Google Cloud Functions API write quota, which limits how many deployment operations you can perform per minute. When you deploy functions, the Firebase CLI makes API calls to the cloudfunctions.googleapis.com service to create or update each function. If too many deployment requests are made in a short time period, Google Cloud returns an HTTP 429 "Too Many Requests" status code to prevent API overload. This quota exists to protect Google's infrastructure and ensure fair usage across all projects. The write quota specifically controls deployment operations (creating, updating, or deleting functions) and is separate from quotas that govern function execution or invocation. Importantly, this is a fixed quota that cannot be increased through standard quota increase requests. The error most commonly occurs in CI/CD environments where automated deployment pipelines attempt to deploy all functions at once, or when developers deploy large numbers of functions using a single `firebase deploy --only functions` command.

Typical symptoms

  • Deployment fails with "HTTP Error: 429, Quota for Google Cloud Functions API exceeded"
  • Error message references cloudfunctions.googleapis.com quota limits
  • Deployment succeeds for some functions but fails partway through
  • CI/CD pipeline fails at the Firebase deployment step
  • Subsequent deployments within minutes also fail with 429 errors
  • Firebase CLI shows "Quota exceeded" or "Rate limit exceeded" messages

Common causes

  1. Deploying too many Cloud Functions simultaneously in a single command
  2. CI/CD system making rapid sequential deployments without rate limiting
  3. Multiple developers or pipelines deploying to the same project concurrently
  4. Large codebase with 50+ functions being deployed at once
  5. Automated deployment scripts that don't implement batching or delays
  6. Retry logic that immediately redeploys after a quota error, compounding the issue

How to fix "Cloud Functions: HTTP 429 - Quota exceeded when deploying functions"

1Wait for quota reset

The API quota resets automatically after a time window (typically 1 minute). Wait 1-2 minutes before attempting another deployment:

bash
# Wait before retrying
sleep 120
firebase deploy --only functions

This simple pause often resolves the immediate issue and allows your next deployment to succeed.

2Deploy functions in small batches

Instead of deploying all functions at once, deploy them in groups of 10 or fewer using the --only flag:

bash
# Deploy specific function groups
firebase deploy --only functions:userAuth,functions:dataProcessor,functions:emailSender

# Or deploy individual functions
firebase deploy --only functions:sendWelcomeEmail
firebase deploy --only functions:processPayment

This reduces the number of API calls made in a short time period and stays within quota limits.

3Implement sequential deployment script

Create a deployment script that deploys functions sequentially with delays between batches:

javascript
// deploy-functions.js
const { execSync } = require('child_process');
const fs = require('fs');

// Get all function names from firebase.json or functions/index.ts
const functionNames = [
  'userAuth',
  'dataProcessor',
  'emailSender',
  'webhookHandler',
  // ... add all your functions
];

const BATCH_SIZE = 10;
const DELAY_MS = 5000; // 5 second delay between batches

async function sleep(ms) {
  return new Promise(resolve => setTimeout(resolve, ms));
}

async function deployInBatches() {
  for (let i = 0; i < functionNames.length; i += BATCH_SIZE) {
    const batch = functionNames.slice(i, i + BATCH_SIZE);
    const functionList = batch.map(name => `functions:${name}`).join(',');

    console.log(`Deploying batch ${Math.floor(i / BATCH_SIZE) + 1}: ${batch.join(', ')}`);

    try {
      execSync(`firebase deploy --only ${functionList}`, { stdio: 'inherit' });
      console.log('Batch deployed successfully');
    } catch (error) {
      console.error('Batch deployment failed:', error.message);
      process.exit(1);
    }

    if (i + BATCH_SIZE < functionNames.length) {
      console.log(`Waiting ${DELAY_MS / 1000} seconds before next batch...`);
      await sleep(DELAY_MS);
    }
  }
}

deployInBatches();

Run with: node deploy-functions.js

4Configure CI/CD pipeline for rate limiting

Update your CI/CD configuration to deploy functions in batches. Example for GitHub Actions:

yaml
# .github/workflows/deploy.yml
name: Deploy Firebase Functions

on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3

      - name: Setup Node.js
        uses: actions/setup-node@v3
        with:
          node-version: 18

      - name: Install dependencies
        run: npm ci

      - name: Deploy batch 1
        run: firebase deploy --only functions:batch1FuncA,functions:batch1FuncB
        env:
          FIREBASE_TOKEN: ${{ secrets.FIREBASE_TOKEN }}

      - name: Wait
        run: sleep 10

      - name: Deploy batch 2
        run: firebase deploy --only functions:batch2FuncA,functions:batch2FuncB
        env:
          FIREBASE_TOKEN: ${{ secrets.FIREBASE_TOKEN }}

For GitLab CI:

yaml
# .gitlab-ci.yml
deploy:
  stage: deploy
  script:
    - firebase deploy --only functions:groupA
    - sleep 10
    - firebase deploy --only functions:groupB
    - sleep 10
    - firebase deploy --only functions:groupC
  only:
    - main
5Check current quota usage in Google Cloud Console

Monitor your actual quota usage to understand your limits:

1. Go to the Google Cloud Console: https://console.cloud.google.com
2. Select your Firebase project
3. Navigate to IAM & Admin > Quotas
4. Search for "Cloud Functions API"
5. Look for "Write requests per minute" quota

You can view current usage and limits here. Note that the deployment write quota typically cannot be increased, so you must work within the existing limits.

6Use selective function deployment during development

During active development, deploy only the functions you're currently working on:

bash
# Deploy only the function you modified
firebase deploy --only functions:myNewFunction

# Or use function groups defined in firebase.json
firebase deploy --only functions:auth

This reduces unnecessary deployments and conserves your quota for when you need full deployments.

Advanced notes

Understanding Firebase Functions API Quotas: The Cloud Functions API has separate quotas for different operations. The WRITE quota (which governs deployments) is distinct from READ quotas (listing functions) and CALL quotas (invoking functions via the API). The deployment quota is intentionally conservative to prevent infrastructure overload and cannot be increased through quota requests, unlike some other Google Cloud quotas.

Function Grouping Strategy: For large projects, organize your functions into logical groups in your codebase (e.g., auth.ts, data.ts, notifications.ts) and deploy groups separately. This makes selective deployments easier and naturally batches your deployments.

Handling Deployment Failures: If a batch deployment fails partway through, Firebase Functions are designed to be idempotent. You can safely retry the same deployment command - functions that were successfully deployed won't be redeployed unnecessarily, only failed or pending functions will be processed.

First vs Second Generation Functions: This quota applies to both Cloud Functions 1st gen and 2nd gen. However, 2nd gen functions (built on Cloud Run) may have different performance characteristics. If you're experiencing frequent quota issues, consider whether your deployment strategy could be optimized regardless of function generation.

Alternative: Use Firebase Extensions: For common functionality, consider using Firebase Extensions instead of custom functions. Extensions are pre-built and don't count against your deployment quota since they're installed rather than deployed.

Frequently asked questions

What does "429" mean?
This error indicates that your Firebase project has exceeded the Google Cloud Functions API write quota, which limits how many deployment operations you can perform per minute. com service to create or update each function. If too many deployment requests are made in a short time period, Google Cloud returns an HTTP 429 "Too Many Requests" status code to prevent API overload.
How do I fix "429"?
This HTTP 429 error occurs when you exceed Firebase's API rate limits while deploying Cloud Functions, typically when deploying many functions simultaneously or in rapid succession through CI/CD pipelines.
What causes "429"?
Deploying too many Cloud Functions simultaneously in a single command CI/CD system making rapid sequential deployments without rate limiting Multiple developers or pipelines deploying to the same project concurrently
Is the "429" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading