Skip to content
This repository has been archived by the owner on Nov 29, 2023. It is now read-only.

Commit

Permalink
MV-10296 Remove incorrect exclusion to retry policy (#1157)
Browse files Browse the repository at this point in the history
* As of MV-6709, we will still retry non-2xx responses, even for large response sizes.
  • Loading branch information
tpensyl authored Sep 20, 2023
1 parent 23d4836 commit b856296
Showing 1 changed file with 0 additions and 1 deletion.
1 change: 0 additions & 1 deletion site/docs/messaging/webhooks.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,6 @@ Bandwidth uses HTTP Callbacks webhooks to send events to any publicly addressabl
* All Message callbacks are sent as a list/array `[ {message metadata} ]` to the webhook url in the application.
* You **MUST** Reply with a `HTTP 2xx` status code for _every_ callback/delivery receipt. Bandwidth will retry _every_ callback over the next 24 hours until a `HTTP 2xx` code is received for the callback. After 24 hours, Bandwidth will no longer try to send the callback.
* Bandwidth's Messaging platform has a 10 second timeout for callbacks. This means your server must respond to the callback request within 10 seconds, otherwise the platform will try again at a later time.
* Your server should return a response smaller than 16kB. If the reponse is larger, Bandwidth will not retry the callback.
* Because we guarantee "at least once delivery" of events, it is possible (but not common) to receive duplicate message events. Your server should be able to handle duplicates.

## Inbound Message Webhooks
Expand Down

0 comments on commit b856296

Please sign in to comment.