Closed DaveBagler closed 3 years ago
The issue is just on the initial send. I added a status callback webhook. If the status is sent, failed, delivered or undelivered, I've added a fetch, and I update the message in the database. The fetch provides the timestamps in the correct timezone.
Hi @DaveBagler the timestamps on the messages are set at the API layer in UTC when you make a call and this is not a helper library issue. That said, have you set a timezone in your Twilio project? I would also recommend reaching out to support if you need more help.
Thanks, I'll reach out to Twilio for support. It does seem like it's not setting UTC on the initial call but then updating it to UTC on fetch.
Issue Summary
When I send an SMS message from my application the Created timestamp is in my local timezone (EST) however the documentation says it should be UTC. When I receive an SMS message through the webhook the Created timestamp is correctly in UTC. This creates a sorting issue in my database log of SMS messages.
Steps to Reproduce
SendMessage
.)RetrieveMessageDetails
.)Code Snippet
Exception/Log
N/A
Technical details: