Question

Why does Request Inspector list requests with call statuses out of order?

Product

Programmable Voice

Answer

In rare situations where a call ends almost immediately after it begins, you may notice that the Completed status callback appears in the Request Inspector before the webhook request to the Voice URL with the In-Progress status. This can give the impression that the call was completed before it ever reached the in-progress state.

This happens because status callbacks are handled asynchronously, and Twilio orders entries in the Request Inspector based on the timestamps of when requests are sent and responses are received. For example, if the webhook request is sent at 12:30:01 and the status callback request is sent at 12:30:02, but Twilio receives the response for the status callback at 12:30:03 and the response for the webhook at 12:30:04, the Request Inspector will display the status callback first, followed by the webhook request.

Additional Information 

Tracking the Status of an Outbound Twilio Voice Call