We have been having timestamps problems on a few Taiwan RICs. Please see below snippet for 4132.TWO. This particular message came around 07:07:53 UTC (of 2020-05-26), however the TRdTIM_1 FID had 16:00:00.000000000. This kind of message with incorrect timestamp is very rare, but it does happen. Could you explain why this is the case? We're using RFA C++ API v8.x.x on Elektron platform. thanks.
Hello @jzhao and all,
The report was investigated by Refinitiv content experts, the conclusion was:
"Resolution:"The particular message came around 07:07:53 UTC (of 2020-05-26) is amended trade.
Updates with TRDTIM_1 FID & EXCHTIM value equal to 16:00:00.000000000 are amended trade. Please use this to filter out amended trade. "
I see the update at point in TickHistory Raw extraction for 05/26. To me it also is not clear why TRDTIM_1 would be so dissimilar to timestamp of the update and to the same field in the updates that were close in time, the previous and the next updates.
This being content-specific question and suspected issue with content at point, as a customer, the best way to get it investigated by the corresponding content expert is to submit this description at Refinitiv Content Helpdesk Online.
Would you prefer to proceed and open the case on content directly, or I can help to open one on your behalf?