By default, each task runs for a maximum of 10 minutes: you can change this to a shorter time or a longer time up to 168 hours (7 days). Support for timeouts greater than 24 hours is available in Preview . For tasks using GPUs, the maximum available timeout is 1 hour.
You set task timeout as described in this page. There is no explicit timeout on a job execution: when all tasks are done, the job execution is done.
The units specify a duration. You can specify the timeout duration as an integer
value in seconds, minutes, or hours. For example, to set the timeout duration as
10 minutes and 5 seconds, specify the value as 605
seconds.
If your job has retries enabled, the timeout setting applies to each attempt of a task. If the task attempt does not complete within this time, it will be stopped. The longer a job runs, the more likely it is to run into issues that cause it to fail, such as downstream dependency failures, out of memory errors, or infrastructure issues. We recommend enabling retries for all jobs, but especially for jobs with long-running tasks.
Maintenance events
Jobs periodically undergo maintenance events. During a maintenance event, any in-progress tasks are migrated from the current machine to a different machine. There is a brief pause in processing while the task is migrated.
The migration process preserves the state of the task, with one notable exception: outbound VPC network connections break during maintenance events. We recommend that you use client libraries that can handle occasional connection resets.
Cloud Run prints out a log message every time a task starts and finishes migrating.
Additionally, if you want to monitor or handle maintenance events in a specific way,
you can catch the SIGTSTP
signal, which is sent 10 seconds before a task is
migrated. After migration, the task receives a SIGCONT
signal immediately
after the task is restarted.
The following Go sample is a function that catches these signals and prints out a log entry:
func testSignals () { sigs := make ( chan os . Signal , 1 ) signal . Notify ( sigs , syscall . SIGTSTP , syscall . SIGCONT ) go func () { for { sig := < - sigs log . Printf ( "Got Signal: %v" , sig ) } }() }
Required roles
To get the permissions that you need to configure Cloud Run jobs, ask your administrator to grant you the following IAM roles:
- Cloud Run Developer
(
roles/run.developer) on the Cloud Run job - Service Account User
(
roles/iam.serviceAccountUser) on the service identity
For a list of IAM roles and permissions that are associated with Cloud Run, see Cloud Run IAM roles and Cloud Run IAM permissions . If your Cloud Run job interfaces with Google Cloud APIs, such as Cloud Client Libraries, see the service identity configuration guide . For more information about granting roles, see deployment permissions and manage access .
Set task timeout
To specify task timeout for a Cloud Run job:
Console
-
In the Google Cloud console, go to the Cloud Run jobs page:
-
Select Jobsfrom the menu, and click Deploy containerto fill out the initial job settings page. If you are configuring an existing job, select the job, then click Edit.
-
Click Container(s), Volumes, Connections, Securityto expand the job properties page.
-
Click the Generaltab.
- In the Task timeoutfield, specify the maximum duration for the job tasks in
the current job, and select a Time unit. You can only specify the timeout duration
as an integer value in second, minute, or hour. For example, to set a
duration of 10 minutes and 5 seconds, in the Task timeoutfield, specify
605, and select the Time unitas second.
- In the Task timeoutfield, specify the maximum duration for the job tasks in
the current job, and select a Time unit. You can only specify the timeout duration
as an integer value in second, minute, or hour. For example, to set a
duration of 10 minutes and 5 seconds, in the Task timeoutfield, specify
-
Click Createor Update.
gcloud
-
For a job you are creating:
gcloud run jobs create JOB_NAME --image IMAGE_URL --task-timeout TIMEOUT
Replace
- JOB_NAME with the name of your job.
- IMAGE_URL
: a reference to the container image
—for
example,
us-docker.pkg.dev/cloudrun/container/job:latest. - TIMEOUT
with the maximum duration for the job tasks,
specifying the amount of time and the units: for example,
10m5sis ten minutes and five seconds.
-
For a job you are updating:
gcloud run jobs update JOB_NAME --task-timeout TIMEOUT
YAML
-
If you are creating a new job, skip this step. If you are updating an existing job, download its YAML configuration :
gcloud run jobs describe JOB_NAME --format export > job.yaml
-
Update the
timeoutSeconds:attribute:apiVersion : run.googleapis.com/v1 kind : Job metadata : name : JOB spec : template : spec : template : spec : containers : - image : IMAGE timeoutSeconds : TIMEOUT
Replace:
- JOB_NAME with the name of your job.
- IMAGE_URL
: a reference to the container image
—for
example,
us-docker.pkg.dev/cloudrun/container/job:latest. - TIMEOUT
with the maximum duration for the job tasks,
specifying the amount of time and the units. You can only specify time
as an integer value in seconds, minutes, or hours. For example, to set
a duration of 10 minutes and 5 seconds, specify
605.
You can also specify more configuration details, such as environment variables or memory limits.
-
Update the existing job configuration:
gcloud run jobs replace job.yaml
Terraform
To learn how to apply or remove a Terraform configuration, see Basic Terraform commands .
Add the following to agoogle_cloud_run_v2_job
resource in your Terraform configuration:View task timeout settings
To view the current task timeout settings for your Cloud Run job:
Console
-
In the Google Cloud console, go to the Cloud Run jobs page:
-
Click the job you are interested in to open the Job detailspage.
-
Click View and Edit job configuration.
-
Locate the task timeout setting in the configuration details.
gcloud
-
Use the following command:
gcloud run jobs describe JOB_NAME
-
Locate the task timeout setting in the returned configuration.
