A Cloud Run job task exited 0 on its own, about 3 minutes before its task timeout. The execution stayed non-terminal (we could see it still running in the console), then was marked failed with “The configured timeout was reached” while its logs reported clean exit code 0. There is no SIGTERM or SIGKILL log.
Execution
- Project: <redacted, available for support>
- Region:
europe-west9 - Job: <redacted, available for support>
- Execution: <redacted, available for support>
- Execution environment: gen2
taskCount: 1,maxRetries: 0,timeoutSeconds: 3800- Operation id: <redacted, available for support>
Timeline (UTC)
| Time | Event |
|---|---|
| 2026-09-28T07:30:03.214Z | startTime |
| 2026-09-28T08:30:19.323Z | Application logs Max lifetime (3600s) ... reached, stopping and Completed execution |
| 2026-09-28T08:30:19.600Z | System log Container called exit(0). (run.googleapis.com/varlog/system, ingested at 08:30:19.607Z) |
| 2026-09-28T08:33:23Z | Task timeout deadline (startTime + 3800s) |
| 2026-09-28T08:48:28.654Z | completionTime. Completed=False: Task <redacted, available for support> failed with exit code: 0 and message: The configured timeout was reached. |
| 2026-09-28T08:48:29.784Z | System audit event, status.code 4: Execution<redacted, available for support>has failed to complete, 0/1 tasks were a success. |
No application or system logs exist between the exit and the audit event. failedCount is 1. The Retry condition is ImmediateRetry for attempt 0, and no second attempt started.
Expected: an execution whose container logs Container called exit(0). before startTime + timeoutSeconds is succeeded, with completionTime near that exit.
Actual: the Jobs API still had the execution running at the timeout deadline, then closed it 15 minutes later as a timeout failure with exit code 0.
We do hit this same issue several times a week.