Incorrect webhook client endpoint URLs
Incident Report for Batch
Resolved
On 2024-03-11, we deployed an update of our webhook service.
It resulted in incorrect client HTTP paths: they were suffixed either by /Oauth2, /Basic or /StaticKey

Therefore, endpoints that could not route those URLs were not able to handle the webhooks and Batch flagged them as failed.
Some endpoints with more permissive configurations were not affected.

We rolled back our service on 2024-03-14 at 5PM UTC, which resolved the issue. As the service started replaying non-expired failed requests, you might have got some slightly older events depending on your configuration.

As the failed webhook events have expired and been deleted from our system, they will not be replayed.
Posted Mar 14, 2024 - 18:00 UTC
← Current Status Powered by Atlassian Statuspage