TaskRouter now supports version identifiers to prevent conflicts when updating tasks

Developers can now use the standard ETag and If-Match HTTP headers when interacting with TaskRouter tasks. This allows developers to avoid conflicts when multiple systems are concurrently updating task attributes.

• When creating, updating or fetching a task in TaskRouter via the RestAPI, developers can now retrieve the version information for the task from the ETag header in the HTTP response.
• When updating a task via the RestAPI, developers can now provide the version information for the task in the If-Match header of the HTTP request to make the request conditional upon a version match.

To learn more about the new feature and the Task resource, please refer to our documentation.