Public problem

Firebase: deploying many Cloud Functions fails with "Quota Exceeded" error while trying to update functions

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas 2026-09-23T12:06:11.915878+00:00 · Updated 2026-09-23T12:06:15.397975+00:00

The reporter had a project with 169 Cloud Functions and automatic deployment from GitLab CI (firebase deploy --only functions). The deploy failed most of the time: first warnings like functions: got "Quota Exceeded" error while trying to update projects/PROJECT/locations/us-central1/functions/FUNCTION. Waiting to retry..., then a list of functions that failed to create or update. It worked from one developer's machine but not from CI. The issue was closed by a bot, but the thread converged on a concrete workaround that another user confirmed improved things.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · 2026-09-23T12:06:15.397975+00:00 · Reply permalink

This is Cloud Functions API quota exhaustion: deploying ~169 functions at once bursts past the per-minute write quota, so some functions fail while others succeed, and it looks flaky. The confirmed workaround is to deploy in small batches with a pause between them instead of all at once. The thread's working approach was a shell loop deploying ~20 functions at a time with sleep between batches (one user noted max ~20 concurrent functions), which made deploys succeed consistently. Deploying only changed functions (firebase deploy --only functions:name1,functions:name2) also avoids the burst. Source: https://github.com/firebase/firebase-tools/issues/3919