Hi @changgyu,

I have verified historical data from TRTH and found an update with "Add" action for the missing key entry (i.e. NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjQyNw==) sent from Elektron Realtime feed. (Please note that the key actually was base64 encoded. The actual key is "72683426B7161970541472482427".)

Please contact ERT in cloud support via MyRefinitiv to verify the issue.

Below is the detailed information I found when compare data between application log and historical data from TRTH.

- An update was provided to add entry for "72683426B7161970541472482427" key.

HSIN9,Market By Order,2019-07-17T07:01:33.725528358Z,+8,Raw,UPDATE,UNSPECIFIED,,,,9020,,25968,,0
,,,,Summary,,,,,,,,,,2
,,,,FID,4148,,TIMACT_MS,25293631,
,,,,FID,6516,,BOOK_STATE,1,N
,,,,MapEntry,,ADD,,,,,,72683426B7161970541472482427,,9
,,,,FID,14268,,LV_TIM_NS,07:01:33.631438000,
,,,,FID,8591,,ORD_TONE,0,
,,,,FID,6919,,ORDER_PRIY,26284031,
,,,,FID,3428,,ORDER_SIDE,1,BID
,,,,FID,13439,,ORDER_TN,0,"        "
,,,,FID,3429,,ORDER_SIZE,1,
,,,,FID,6529,,LV_DATE,2019-07-17,
,,,,FID,3427,,ORDER_PRC,28562,
,,,,FID,3426,,ORDER_ID,7161970541472482427,

- The update is expected to be added in this entrysequence.txt. ( I have added base64 decoded for Map Entry keys.

Hello @changgyu

I suggest you contact the feed team to verify if the feed sent correct data(delete action on non-existing key) or not. You can contact the feed team via Get Support of MyRefinitiv and select Product to be the feed i.e Thomson Reuters Elektron Real-Time .

Delete action indicates that the consumer should remove any stored or displayed information associated with the entry. As far as I understand, for delete action on non-existing key case, it is possible that the application will ignore the delete action because the key does not exist when the delete action comes. Normally, delete action should for existing key so you should contact the feed team to verify data as well.