What's the timeout for Node cloud tasks handlers?

[Konrad Garus]

I have an application that does some work in background, using default Cloud Tasks for scheduling/executing the process.

I would like the job to be able to run for a few minutes, or at least understand what the actual limitations are and what I can do about them.

According to docs on Push Queues (which seem to be equivalent to the modern Cloud Tasks?), the deadline is 10 minutes: https://cloud.google.com/appengine/docs/standard/python/taskqueue/push/#the_task_deadline.

However, my job seems to crash after 2 minutes. 115 seconds is fine, 121 seconds is a crash. The workload and resource consumption is the same in all cases. The message is always the unhelpful "The process handling this request unexpectedly died. This is likely to cause a new process to be used for the next request to your application. (Error code 203)".

According to docs on Node request handling, there is a 60-second timeout: https://cloud.google.com/appengine/docs/standard/nodejs/how-requests-are-handled.

What is the timeout in the end? Is it 1 minute, 2 minutes, or 10 minutes? Is there anything I can do to change it, if I want my job to run for 5 or 30 minutes?

[Dan S (Cloud Platform Support)]

Hello,

As I understand the documentation confirm that "Automatic scaling services must finish before 10 minutes". Therefore, it seems that it will accept if the task falls in 2 minutes. You should get a better assistance in the Stack Overflow[1] since you have a technical issue and it will require some troubleshooting. 

There, you should receive help from the community fellow enthusiasts, and from Google engineers when you add a tag in your post according to the product where you require assistance, as you can check in our documentation[2]. Additionally, I suggest that you post some sample code and details regarding your application like deployment and settings.

[1] http://stackoverflow.com/

[2] https://cloud.google.com/support/docs/stackexchange