You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
When setting an exponential backoff strategy for the client, is there a way to distinguish between a failed connection (for exemple if the engine server is down) and an empty list of retrieved tasks ?
I found that the BackoffJobAcquisitionStrategy can suit the needs, but I can't see how to relate it with the client.
Thanks for the help
Edit : to be more precise, I would like to have the back off only when failing to connect to the server. If the connection is ok but the list of tasks is empty, then we retry ~immediately.
The text was updated successfully, but these errors were encountered:
Hi,
When setting an exponential backoff strategy for the client, is there a way to distinguish between a failed connection (for exemple if the engine server is down) and an empty list of retrieved tasks ?
I found that the BackoffJobAcquisitionStrategy can suit the needs, but I can't see how to relate it with the client.
Thanks for the help
Edit : to be more precise, I would like to have the back off only when failing to connect to the server. If the connection is ok but the list of tasks is empty, then we retry ~immediately.
The text was updated successfully, but these errors were encountered: