Closed ExpandedVenture closed 2 years ago
I performed this data correction manually:
update lnchat set delete_time=null where delete_time is not null and id='1C189250-2ED7-4306-828F-C7293B5EB7EA';
update lnchat set delete_time=null where delete_time is not null and id='EBD7C4FA-745E-4E6B-BBA1-8B2B6119ECE7';
update lnchat set delete_time=null where delete_time is not null and id='965C4701-35CA-4C88-96FA-D31FCAB93A8C';
update lnchat set delete_time=null where delete_time is not null and id='B457C83D-D081-4375-9A6B-EAB1FABDD001';
update lnchat set delete_time=null where delete_time is not null and id='99D09270-D54C-41BF-A9F8-1A6C68DA5099';
The convedsations was always stored in our database. When the scraping process uses tu submit the scrapend chats, from the first one, and it fails due any communication error at the middle of the upload, and the remaining chats are flaged as deleted.
I just released a fix-patch.
But this incident is still under revision.
Fixed.
Reference: https://euler.connectionsphere.com/drl/responses?rid=81688FB6-B4E3-4726-ABB9-794D91A7138A