Google cloud run Job timeout not triggering

[1zero1]

I have a job, configured with a 10 minute timeout. I have manually stopped the job after 20 minutes.

What should I check? How to understand what is wrong with the configuration?

[VishalBulbule]

Have you checked logs?

[1zero1]

@VishalBulbule ,

Yes nothing there to help.

My app is running "normally".  Meaning that , for test purpose, I have make sure there is a continuous loop. Logs show the app is still running.

What should I look for in the logs? You're talking about the running job logs right?

[aaronlerner]

Thanks for reporting! We identified the issue and had been working to fix over the last couple months. That fix is now live and you should no longer encounter this issue. Please let us know if you see it again.

[robin-tapraise]

Hi Aaron,

I have set a task timeout for 4 minutes, but it usually takes between 8-12 minutes before the timeout actually triggers. Is this a known issue or something to be fixed from my end?

Kind regards,

Robin van Wijngaarden

[aaronlerner]

Hi Robin, I took a look at the job execution in your screenshot and the reason it's running for 8-9 minutes is because your job is configured to allow 1 retry. The first attempt runs and times out after 4 minutes, then a second (retry) attempt runs and also times out after 4 minutes. You can see this in your screenshot in the left-side panel where it says "Retries: 1" and in the right-side panel where it says "Number of retries....1"

You can set this field to 0 to disable retries. See https://cloud.google.com/run/docs/configuring/max-retries for more information on how to view and configure this setting.

[robin-tapraise]

Ah, damn. My bad. Thanks for pointing that out!