Web Hooks - back-off for 429 Too Many Requests
Proposal
We currently consider all 4xx
responses for web-hooks to be evidence they are
misconfigured. Too many in a row result in the hook being disabled until users
intervene to reenable them.
However, the response 429 - Too many requests
should get different behavior:
we should:
- Back-off immediately (not after 3 such responses), since we have been told to back-off
- Honour the
Retry-After
header
Implementation details
This should be relatively straightforward, and would be a change to the
LogExecutionService#update_hook_failure_state
method, to add a new condition.