ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Timeout limits and cleanup in Cloud Functions Firebase Cloud Functions impose a hard timeout that terminates the execution thread when exceeded. In 1st‑gen functions the default is 60 s, extendable to 540 s; 2nd‑gen HTTP functions can run up to 3600 s. When the timeout fires, the runtime stops the function instance and any code scheduled after that point is
Compatibility conflict between Admin SDK v11+ and Cloud Functions 1st gen runtime Deploying a Cloud Function that depends on Firebase Admin SDK v11.0.0 or later to a 1st gen Node.js 12 runtime fails at initialization with the error FirebaseAdminError: This version of the Admin SDK requires Node.js 14 or later . The 1st gen Node.js 12 runtime reached end-of-l
Teams need to decide how to handle Firebase Alerts to keep notification volume manageable without missing important signals. The default console configuration sends every alert email to all project members, offering no built‑in way to scope messages by alert type or individual recipient. An alternative is to intercept alerts with Cloud Functions 2nd gen fire
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"
firebase