Will HTTP/1.1 429 Responses automatically send an Element into Timeout?
Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 7th July 2023
Below you can find the logic that is applied to timeout handling in terms of HTTP status codes ranges:
- 2XX: No timeout
- 3XX:
customRedirect enabled and the redirect is not properly handled: Timeout
customRedirect disabled and the redirect is properly handled: No Timeout - 4XX: Timeout
- 5XX: Timeout
As a result 429 Too Many Requests will automatically put the element in timeout if the last retry of the configured amount of retries on that connection still results in a 429 Too Many Requests or another one in the timeout range.
Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 7th July 2023