Webhook implementations see 202 as an error.

[AkbarTheGreat]

The webhook receiver I'm using sends back 202 ("Accepted") on a successfully accepted webhook. Because Keel views this as an error, it retries each webhook several times, spamming the receiver.

level=error msg="could not send notification via notifier" error="got status 202, expected 200/201" notification name="update resource"

I see this with the generic webhook sender as well as the Mattermost sender.

[immanuelfodor]

Came here to say the exact same thing. If it adds value, I send the webhook to a generic webhook receiver (no matter the payload format) powered by Matrix Hookshot. It also returns 202 when not waiting for the response from Matrix (which makes sense, the webhook was indeed Accepted, but not sure if it can be delivered to Matrix, still returning a 2XX success response to Keel). I'd like Keel to accept 202 as success, too, not just 200/201.

[immanuelfodor]

HTTP 202 explanation for reference: https://http.cat/status/202 (I love these cats😄)

[immanuelfodor]

BTW, it seems fairly simple to extend the list of accepted codes

[immanuelfodor]

For other Hookshot users: the immediate workaround is to set waitForComplete: true instead of false for the Keel webhook until a fix for Keel is released. (Either set globally, or per static webhook.)