Quick answer
Google Cloud Functions documents control-plane api rates as Read and write quotas vary by generation and region. Deployment and management API quotas are separate from requests to deployed functions.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| control-plane API ratesDeployment and management API quotas are separate from requests to deployed functions. | Read and write quotas vary by generation and region | Per project | Google CloudAug 22, 2026 |
Why does this limit matter?
High-frequency deployment automation can be throttled even while function traffic is healthy.
This value is scoped to Per project; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Use Cloud Quotas for the project and separate admin calls from runtime traffic metrics.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Quota values and increase eligibility differ by operation and generation.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related