Unexpected 429/503 errors with max_instances set to 0 in Cloud Functions
Scaling limits in Cloud Functions (2nd gen) When configuring a Cloud Function, setting max_instances to 0 is intended to remove the explicit upper bound on the number of concurrent instances the platform can spin up to handle incoming traffic. However, there is uncertainty regarding whether an internal platform hard cap exists that overrides this "unlimited"