My queue is running unexpected retries on tasks where attemptDispatch results in an error as seen in attemptResponse. Normally the queue doesn't execute retries, which is desired behaviour. For this single task it does; the only difference I notice is that the reason of the failed attempt is an out of memory issue instead of a controlled error response:
My queue is configured with max attempts = 1, see:
The attemptDispatchLog that Google Cloud Tasks writes shows me the following:
This is unexpected as the maxAttempts should most logically be set to 1.
Retries are executed (also unexpected)
This is causing duplicate runs that are not expected, which is causing trouble in our system. We are moving towards idempotent jobs as suggested by the Cloud Tasks documentation. But still we would like to know what is going on in this scenario.