Today the ETOS Client will retry when triggering the ETOS API, this is fine. The problem is that when there is a Bad Request, then the client will retry as well even though it will never be possible to start when there is a Bad Request.
Motivation
No need to hammer the API with retries when there is not chance of success.
Exemplification
Self-explanatory
Benefits
The API does not have to be scaled up for hammering of bad requests.
Description
Today the ETOS Client will retry when triggering the ETOS API, this is fine. The problem is that when there is a Bad Request, then the client will retry as well even though it will never be possible to start when there is a Bad Request.
Motivation
No need to hammer the API with retries when there is not chance of success.
Exemplification
Self-explanatory
Benefits
The API does not have to be scaled up for hammering of bad requests.
Possible Drawbacks
None