connection.resume() seems to have some sort of connection state bug

[robertito121]

we are calling connection.resume() in a loop for multiple connections that are on-hold and even on, as little as, 2 connections, connection.resume() throws the following error.

Connection with connection id <connection_id> failed to be resumed with error{"type":"CallAlreadyResumedException","message":"Error received from Voice Service","stack":["CallAlreadyResumedException","

This is definitely an invalid error because the connection ID that is referenced in those errors is still on hold. We did triple check that the loop is not trying to call connection.resume() on the same connection object we have already resumed. However, the way we were able to determine a bug on connection.resume() is by placing a set timeout in between each connection in the loop, and the only time we did not encounter this error was when calling connection.resume() after 3 ms apart from each connection. 2 or less throws the error consistently.

We have had this use case coded in our CPP for a while and was working fine with no issues but updating to a newer stream API version broke this use case for us. We have a button to resume all connections that are on-hold with a single click of the button but of course, with this bug, the button now only resumes each connection at a time.