JavaScript Calling SDK has a built-in retry mechanism when the browser loses network connectivity

Question

According to the Azure Communication Services documentation, the JavaScript Calling SDK has a built-in retry mechanism when the browser loses network connectivity. I would like to know the exact behavior of this retry mechanism.

Does the ACS Calling SDK use one of the following retry strategies?

1.Exponential back-off. The application waits a short time before the first retry and then exponentially increases the time between each subsequent retry. For example, it might retry the operation after 3 seconds, 12 seconds, 30 seconds, and so on.

2.Incremental intervals. The application waits a short time before the first retry, and then incrementally increases the time between each subsequent retry. For example, it might retry the operation after 3 seconds, 7 seconds, 13 seconds, and so on.

3.Regular intervals. The application waits for the same period of time between each attempt. For example, it might retry the operation every 3 seconds.

4.Immediate retry. Sometimes a transient fault is brief, possibly caused by an event like a network packet collision or a spike in a hardware component. In this case, retrying the operation immediately is appropriate because it might succeed if the fault is cleared in the time that it takes the application to assemble and send the next request. However, there should never be more than one immediate retry attempt. You should switch to alternative strategies, like exponential back-off or fallback actions, if the immediate retry fails.

5.Randomization. Any of the retry strategies listed previously can include a randomization to prevent multiple instances of the client sending subsequent retry attempts at the same time. For example, one instance might retry the operation after 3 seconds, 11 seconds, 28 seconds, and so on, while another instance might retry the operation after 4 seconds, 12 seconds, 26 seconds, and so on. Randomization is a useful technique that can be combined with other strategies.

Answer 1

The Azure Communication Services (ACS) JavaScript Calling SDK does indeed have a built-in retry mechanism for handling network connectivity issues. However, the specific details regarding the exact behavior of this retry mechanism, including the strategy it employs (such as exponential back-off, incremental intervals, regular intervals, immediate retry, or randomization), are not explicitly detailed in the provided context.

To get the most accurate and detailed information regarding the retry strategies used by the ACS Calling SDK, it is recommended to consult the official Azure Communication Services documentation directly. This will provide the latest updates and specific implementation details regarding the SDK's retry behavior.

---

References:

• Recommendations for handling transient faults
• Transient fault handling
• Azure Functions error handling and retries (programming-language-javascript)
• Retry Storm antipattern
• Azure Functions error handling and retries (programming-language-javascript)