Cloud Run request timeout reverts back to 60 after every update

74 Views Asked by At

I have a Cloud Scheduler job that runs each day and takes around 12 minutes to complete. I updated the timeout limit to 30 minutes for both the job and the Cloud Run container. Whenever I update the script of the job, the Cloud Run container's timeout drops back down to 60 seconds. I change the timeout via Cloud Shell and run:

gcloud beta run services update dailyupdates --timeout=1800s

Is there a way to make prevent the timeout setting from defaulting back?

1

There are 1 best solutions below

7
Rainy sidewalks On

try the following

gcloud beta run services update dailyupdates --timeout=1800s --update-env-vars=MY_TIMEOUT=1800s

EDIT for reference you may want to go through update