In a particular thread(returned by Return all Threads or Return a Thread), at first the latest_message_received_date worked normally. But then when I added more drafts in the thread(due to testing process), at some point latest_message_received_date is null.
Provider: Outlook, EU Server
This is the request_id: 3152380920-50fbce76-ddc0-4014-8336-992e040be98e
When working with the Nylas Threads API, the latest_message_received_date field on a thread represents the timestamp of the most recent received message in that thread. If a thread only contains drafts and no received messages, it is possible for latest_message_received_date to be null, as there are no received messages to provide a value for this field. Adding drafts does not update latest_message_received_date; it only reflects received messages. This field is not documented to be provider-specific, but the presence of only drafts in a thread would explain a null value for latest_message_received_date.
Please let us know if you are experiencing something different than what I’ve described here as we would need to investigate further.
Hi Sam,
thank you for your reply.
What you explained is very naturally understandable.
Nevertheless I‘ve encountered something else.
When I got a brand new email, which does not belong to any particular thread, that email would come with a brand new thread, and the latest_message_received_date is thus not null anymore. Now I keep adding drafts to that thread. At some point(between 10-20 drafts and 1 message), the latest_message_received_date will be null again.
Today I had the same bug again multiple time.
The aforementioned request_id is from the request I tested directly on your Test API website. Please lmk if you need further detail, as I might create a test instance and provide credentials details for you.