Missing keys in delete action when dealing with MarketByOrder domain.

I'm trying to build a book based on Market-By-Order.
But I've observed there are missing keys.

For example,
as for key "NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjQyNw==",
{"Action":"Delete","Key":"NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjQyNw=="} was received but there was no existing entry for the key thsin9.txto delete.

There were a lot of missing keys like this.
Please refer to the attached and below missing keys and advise on how to deal with it properly.

NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjQyNw==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjQ2Mw==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MjQ2OQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MjUxMQ==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU0Ng==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU0Nw==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU5Nw==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU5Ng==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MjYxMg==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU5OA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU5MA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjcyMA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjczNA==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MjgxNQ==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjgyOA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4Mjg5Mw==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4Mjg5Mg==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4Mjg5NQ==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4Mjg5NA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4Mjg5OA==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4Mjk5Ng==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzAxMQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzEyOQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzE1OQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzEzOQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzE5Mg==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzIxNQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzIxOA==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzI2MA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MzI2MQ==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MzI2Mw==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MzMxMA==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzQ2Mg==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MzUwOQ==

NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MzUyMg==

Find more posts tagged with

trep

websockets

rrto

market-by-order

refinitiv-realtime

rdp-api

Accepted answers

veerapath.rungruengrayubkul

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.

All comments

pimchaya.wongrukun01

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.