Quick answer
Google Cloud Run documents maximum task timeout as 168 hours; 1 hour with GPUs. A single job execution can contain up to 10,000 tasks with separate retry controls.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| maximum task timeoutA single job execution can contain up to 10,000 tasks with separate retry controls. | 168 hours; 1 hour with GPUs | Cloud Run jobs | Google CloudAug 22, 2026 |
Why does this limit matter?
GPU selection changes the task ceiling from seven days to one hour.
This value is scoped to Cloud Run jobs; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Inspect task timeout, GPU use, task count, retries, and orchestration deadlines.
- 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
- Job task timeout is not an HTTP request timeout and retries can extend total workflow time.
- 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