IssueTracker

This will create a public issue which anybody can view and comment on.

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: Users reported that Cloud Tasks were not being processed and were repeatedly retried with the error message "Reason to retry UNKNOWN(2): HTTP status code 0". This issue caused significant disruption to their production environment.

What you expected to happen: The tasks were configured properly as per documentation, so the expectation was that they were executed successfully.

Root cause: An internal code change introduced a regression that caused the backend to require the audience field in the httpTarget.oidcToken configuration for Cloud Tasks when using the BufferTask API, even though the documentation listed it as optional.


Other information (workarounds you have tried, documentation consulted, etc):

Workaround: Explicitly specifying the audience field in the httpTarget.oidcToken configuration when using the BufferTask API.

Next Steps: There is a fix in development. Since there is no certain ETA, this public ticket will track progress.