Twilio Changelog | May. 14, 2023

Introducing Retries with Exponential Backoff in TaskRouter SDK V1 & Taskrouter SDK for Flex

We have updated the TaskRouter SDK V1 & Taskrouter SDK for Flex with the introduction of retries and the use of truncated exponential backoff in case of network call failures.

We have updated the TaskRouter SDK V1 & TaskRouter SDK for Flex with the introduction of retries and the use of truncated exponential backoff in case of network call failures.

What's changed?

TaskRouter V1 SDK: We've introduced retries with exponential backoff for each network call to the event bridge for task, worker, and reservation requests. This improvement aims to provide a more reliable experience for users and reduce the need for manual intervention, such as refreshing the browser tab.

TaskRouter SDK for Flex: We've modified the retry mechanism for updating worker activity to use exponential backoff. This improvement will prevent heavy loads on our servers and provide a more reliable experience for users.

Why have we made this change?

Previously, customers might have implemented their own retry mechanisms without proper waiting or backoff strategies, which could lead to less optimal user experiences. By introducing a robust retry mechanism, we aim to ensure a more seamless experience for users.

How to update to this version?

Taskrouter V1 SDK 

TaskRouter SDK for Flex ( for self-hosted or hosted flex) 


For more information and details, please visit the TaskRouter documentation.

Flex TaskRouter