Quick answer
Google Cloud Functions documents request and event payload as Generation and invocation-type specific. HTTP request/response, event, and streaming paths have different documented ceilings.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| 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 |
Why does this limit matter?
Base64-encoded event data can exceed a limit even when the original binary object appeared smaller.
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 trigger, generation, encoding, and intermediate transport before comparing bytes.
- 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
- Event transport services can impose a lower cap before the function receives the payload.
- 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