3scale/issues-test — Issue #553: Webhooks remote error handling
Author: HakubJozak
Created: 2012-02-10 18:08:26+00:00
State: open

When webhooks are called and the remote server responds with 500 or 404, the error is propagated up rather than caught and swallowed. For example

https://3scale.airbrake.io/errors/24953994

-----

From Josep. That is definitely a problem. Also, we need a way to not lose notifications due to poblems on their side:

If the answer from a webhook is not a 200, we should immediately reschedule the notification to be send (ideally after 1minute, but adding delays is not supported by resque). Thus, better do:

Try one, if not 200, put back into the queue and increment a number_of_tries. After X (2 o 3) failures to deliver the notification we put them on a list that is accessible via API call so that they can pulled it when they resolve their issues.

Tasks

https://www.pivotaltracker.com/story/show/21345799