Quick answer
Google Cloud Run documents maximum request timeout as 60 minutes. The configured request timeout can be lower than the platform maximum.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| maximum request timeoutThe configured request timeout can be lower than the platform maximum. | 60 minutes | Cloud Run services | Google CloudAug 22, 2026 |
Why does this limit matter?
Long-running HTTP work remains exposed to client, proxy, and retry behavior even when Cloud Run permits an hour.
This value is scoped to Cloud Run services; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Inspect the service revision timeout and every client or proxy timeout in front of it.
- 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
- Cloud Run jobs use task timeouts rather than service 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