Assigned
Status Update
No update yet.
Comments
ih...@ascentic.se
I also experience a high number of 502 in europe-west1
gh...@google.com
gh...@google.com
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.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
If a task fails even after all its retry attempts have been exhausted it is deleted.
What you expected to happen:
Similar to dead letter topics in Cloud Pub/Sub and dead letter queues in AWS SQS, it'd be beneficial to have dead letter queues for Cloud Tasks.
Steps to reproduce:
Other information (workarounds you have tried, documentation consulted, etc):