Did you try without the purge flag? Was it the same result? Also after purging the delete, did you read the message store to see if you can still find the message? The client apps may not re sync after that.

Please check and let me know.

Funny I woke up and thought about not including the purge flag but have not yet tried it.

I will also check the message store. My intention is only to delete the first outgoing message that I sent so that I will only see incoming responses in my app.

I wouldn't have to do any of this if there was a way to filter to show only incoming messages in the Appliction is that something that we can pay to have implemented?

I just ran this without the purge flag and it is still doing the same thing.

To be clear it's deleting ALL of the agents texts even older ones. It's crippling our company because we don't know what we lost now.

Hi Phong were you able to figure anything out on this?

I just check and here is what I found.

1. Delete a message using the messageId with purge=true will purge your message. Only that particular message will be deleted (removed from your app messaging), not the entire conversation. After that, listing the message store will not show the purged message. But if you call the message-store/[messageId], you can get the following response

{ uri:

   'https://platform.ringcentral.com/restapi/v1.0/account/80964xxxx/extension/5958xxxx/message-store/113275815xxxx',

  id: 113275815xxxx,

  availability: 'Purged',

  lastModifiedTime: '2020-06-05T20:27:48.469Z' }

2. Delete a message using the messageId with purse=false (default value) will delete your message. Only that particular message will be deleted (removed from your app messaging), not the entire conversation. After that, listing the message store will not show the purged message. But if you call the message-store/tmessageId], you can get the following response

{ uri:

 ...

  id: 113276732xxxx,

  to:

   > { phoneNumber: '+165xxxxxx',

       ... } ],

  from:

   { phoneNumber: '+1209xxxxxxx',

     ... },

  type: 'SMS',

  creationTime: '2020-06-05T20:35:22.000Z',

  readStatus: 'Read',

  priority: 'Normal',

  attachments:

   > { id: 113276732xxxx,

       ... } ],

  direction: 'Outbound',

  availability: 'Deleted',

  subject: 'First message from Node JS - See in conversation?',

  messageStatus: 'Delivered',

  smsDeliveryTime: '2020-06-05T20:36:01.000Z',

  smsSendingAttemptsCount: 1,

  conversationId: 6288356833283647000,

  conversation:

   { id: '6288356833283647895',

     ... },

  lastModifiedTime: '2020-06-05T20:36:01.651Z' }

3. Once you delete a message, you cannot call delete it again with purge=true to purge it

4. Once you purge a message (purge=true), you cannot delete it again

If you still have those message Ids, can you call GET message-store/smessageId] to see what is the "availability"?

I am not aware of a way to restore deleted or purged messages. But you can try to send a request to customer support to see if they have a tool to do so.

Thank you for taking a look at this Phong. I will try this shortly . I am not worried about the messages that were already deleted. I only care about getting this process working moving forward.

Will report back soon with findings.

Phong you mentioned earlier that after a message is deleted any further responses from that recipient will no longer sync. Could that be what is happening here?

This is happening from the context of my users and what they are seeing when they are using the Ring Central at app.ringcentral.com (the new online application). This is where the SMS messages are disappearing from.

1) Does deleting the first message cause any subsequent sms messages from that recipient to stop syncing as well in the online application(app.ringcentral.com)?

2) Is it possible to pay for customization to have the ability to filter SMS messages by INCOMING or OUTGOING in the online application (app.ringcentral.com)