Feature Request
Description
As part of https://github.com/elasticio/elasticio/issues/5012 we started re-using http connections so that HTTP timeouts were avoided as a result of there being insufficient outbound IP ports. However, it is still possible in the internet for a certain amount of HTTP timeouts to occur. In principle, this could be solved by adding retry/rebound logic to the component code, however, in practice, this can become quite difficult & tedious (especially if an underlying code library is used). Ideally, Sailor could simply catch thrown exceptions which are caused by HTTP timeouts and auto emit a rebound in those cases.
Definition of Done
Whenever a component's action or trigger's .process() function throws an exception where err.message.code === 'ETIMEDOUT', then sailor should handle that message as a rebound as opposed to an error.
Feature Request
Description
As part of https://github.com/elasticio/elasticio/issues/5012 we started re-using http connections so that HTTP timeouts were avoided as a result of there being insufficient outbound IP ports. However, it is still possible in the internet for a certain amount of HTTP timeouts to occur. In principle, this could be solved by adding retry/rebound logic to the component code, however, in practice, this can become quite difficult & tedious (especially if an underlying code library is used). Ideally, Sailor could simply catch thrown exceptions which are caused by HTTP timeouts and auto emit a rebound in those cases.
Definition of Done
Whenever a component's action or trigger's
.process()function throws an exception whereerr.message.code === 'ETIMEDOUT', then sailor should handle that message as a rebound as opposed to an error.