Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Google Cloud Functions has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 4 scoped observations for Google Cloud Functions. The baseline covers generation-specific maximum, maximum function memory, request and event payload, control-plane API rates. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| 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 |
| maximum function memoryProject and regional quotas also govern aggregate memory use. | 1st gen: 8 GiB; 2nd gen: 32 GiB | Generation specific | Google CloudAug 22, 2026 |
| request and event payloadHTTP request/response, event, and streaming paths have different documented ceilings. | Generation and invocation-type specific | Cloud Run functions | Google CloudAug 22, 2026 |
| 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 |
Tracked constraints and impact
Generation-specific function duration, memory, payload, and API quotas. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
Google Cloud Functions Execution Duration
Google Cloud Functions Execution Duration, verified against Google Cloud Functions's official documentation with scope, implementation impact, caveats, and a direct check.
Google Cloud Functions Memory Limit
Google Cloud Functions Memory Limit, verified against Google Cloud Functions's official documentation with scope, implementation impact, caveats, and a direct check.
Google Cloud Functions Payload Limits
Google Cloud Functions Payload Limits, verified against Google Cloud Functions's official documentation with scope, implementation impact, caveats, and a direct check.
Google Cloud Functions API Quotas
Google Cloud Functions API Quotas, verified against Google Cloud Functions's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Google Cloud Functions baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
1st and 2nd generation time, memory, payload, and API quotas