Quick answer
Google Cloud Functions documents generation-specific maximum as 1st gen: 540s; 2nd gen HTTP: 60m; scheduled: 30m; event: 540s. The maximum depends on generation and invocation type.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| generation-specific maximumThe maximum depends on generation and invocation type. | 1st gen: 540s; 2nd gen HTTP: 60m; scheduled: 30m; event: 540s | Cloud Run functions | Google CloudAug 22, 2026 |
Why does this limit matter?
Migrating to 2nd generation does not give every trigger the 60-minute HTTP ceiling.
This value is scoped to Cloud Run functions; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Identify generation and trigger type, then inspect the deployed timeout setting.
- 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
- Client and hosting timeouts can terminate a request before the function maximum.
- 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