Quick answer
Firebase documents generation-specific function duration as 1st gen: 540s; 2nd gen HTTP: 60m; scheduled: 30m; event: 540s. Generation and trigger type determine the ceiling.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| generation-specific function durationGeneration and trigger type determine the ceiling. | 1st gen: 540s; 2nd gen HTTP: 60m; scheduled: 30m; event: 540s | Cloud Functions for Firebase | FirebaseAug 22, 2026 |
Why does this limit matter?
A 2nd-generation HTTP maximum should not be applied to event-driven functions.
This value is scoped to Cloud Functions for Firebase; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Identify generation, trigger, configured timeout, and any Hosting integration.
- 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
- Hosting rewrites and clients can enforce shorter request timeouts.
- 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