Twilio NuGet: 5.80.0
Currently, webhooks hit (understandably due to async nature) our callback url in random order instead of the order listed under "Message Status Order" in this article.
Could a status timestamp property be added to the message status callback like the voice status callback so we can order them client side like in the Twilio Portal? Or add the status callbacks to the MessageResource for deferred retrieval?
Thank you for reporting the issue. This is outside the scope of the SDK and should be directed to the product team. In order to properly track this feature request, please file a support ticket.
Twilio NuGet: 5.80.0 Currently, webhooks hit (understandably due to async nature) our callback url in random order instead of the order listed under "Message Status Order" in this article.
Could a status timestamp property be added to the message status callback like the voice status callback so we can order them client side like in the Twilio Portal? Or add the status callbacks to the MessageResource for deferred retrieval?