Increase timeout for HTTP tasks to more than 2 hour [178424596]

Assigned

Feature Request

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Jan 26, 2021 09:11AM

Currently, the maximum `dispatch_deadline` value for HTTP tasks is 30 mins:

https://cloud.google.com/tasks/docs/reference/rest/v2/projects.locations.queues.tasks#Task.FIELDS.dispatch_deadline

At the same time, Cloud Run now supports 1-hour timeouts. It would be nice if the queue service will also support 1-hour timeouts.

Comments

am...@google.com <am...@google.com> #2Jan 26, 2021 04:45PM

I also experience a high number of 502 in europe-west1

[Deleted User] <[Deleted User]> #3Jan 26, 2021 11:10PM

We suspect that we may be running into some sort of rate limit. The Cloud Tasks API Quota for maximum requests per minute is rather high (6 million/min) and we're not even close to that, but we believe that when we have bursts of task creation that the API then throws the 502.

am...@google.com <am...@google.com> #4Jan 27, 2021 10:35AM

Assigned to gc...@google.com.

Any update on this? It seems to be happening again. We are experiencing both high latency and 502, the requests are seconds apart.

[Deleted User] <[Deleted User]> #5Jul 3, 2022 09:21AM

Hi,

Are there any updates on this issue? As Cloud Run services support 60 minute timeouts and can be invoked by Cloud Tasks, I think the timeout for HTTP tasks should be extended to 60 minutes when invoking a Cloud Run service.

As it stands, if a Cloud Run service has a timeout of over 30 minutes it will continue to run after the Cloud Tasks request times out. The Cloud Run service will continue to run for up to 60 minutes, but in the meantime the task will be resubmitted because of the 30 minute Cloud Tasks timeout. This seems like a potential source for bugs and user confusion.

Thanks,
Sam

ka...@whatagraph.com <ka...@whatagraph.com> #6Sep 14, 2022 12:09PM

Hi,

any updates?

sq...@gmail.com <sq...@gmail.com> #7Nov 21, 2022 11:19AM

Hello, is it possible to increase the maximum timeout up to 24hours?? because my app user interaction with the app might take an hour up to one day interaction. Or there are other ways??

ge...@blackboxco.com.au <ge...@blackboxco.com.au> #8Apr 11, 2023 10:32PM

Now that we have Cloud Run Jobs, that can also run for up to one hour, this disparity is even more odd. How are these Cloud Run Jobs supposed to be managed in a GCP environment, if not for via Cloud Tasks?

an...@keyplay.io <an...@keyplay.io> #9Sep 27, 2023 09:28PM

Any update on this? It really hamstrings Cloud Tasks to have such a short max timeout.

ra...@google.com <ra...@google.com> #10Apr 26, 2024 04:57PM

Hello, one of my customer have a use case where they have a app which is running on cloud run, but they want the scraper(cloud task) to run in the background so their users can still use the app as the scraper is still scraping.
The scraper is failing and retrying for every 30 mins. Please take this request into consideration on increasing the maximum timeouts for the cloud tasks i.e. more than 2 hours..