Issue Updating a draft in thread unlinks draft from thread

Question and Answers
1

Hello,

I’m having the following issue.

I’m using the node nylas sdk v 7.3.0.

Say I have an email thread.

I start a reply message by creating a draft and specifying the replyToMessageId.

This works fine - I logged into gmail and confirmed there is a new draft linked to the thread.

Once I go back to my application, and update this same draft* via nylas api, the draft becomes unlinked from the original thread.

It is not clear if the replyToMessageId needs to be included in the draft.update request. Regardless, I tried with/without and the unlinking still happens.

create draft transaction id:
22d5b44c-d9ad-4d2a-8205-01c304bdfd3b
update draft transaction id:
87fbe374-47d3-4b0f-97c3-57b25abb2403

edit
NYLAS_API_URI=https://api.eu.nylas.com

2

Hi @Zeal - thanks for posting your question!

So the replyToMessageId value (or reply_to_message_id ) is not persisting across multiple nylas.drafts.update calls. I was able to reproduce this, let me circle back after checking with our Eng team.

1 Like
3

Thank you.

Standing by.

1 Like
4

Also @Zeal - which provider are you using to create the draft? Google, Microsoft?

5

To create the draft I am using:
Google

1 Like
6

Hi @Zeal - the eng team is taking a look, let me circle back as soon as I get any updates :+1:

1 Like
7

Hi @Zeal - let me know if you can try this out now, the thread id should persist across multiple calls :slight_smile: