Not recieving Timestamps in Update messages
Best Answer
-
The RFA API is 'content-agnostic' and will just pass on whatever data it receives from the server.
If you are getting updates without a particular field, then the most likely cause is there was no such field present in that update as sent out by the server.
For example, if you received an update containing something other than a Quote - you would not get a QUOTIM_MS - as the update did not represent Quote type activity.
However, if you feel the above is not a valid explanation for your particular incidents, then please raise Content incorrect/incomplete type ticket at MyRefinitiv - with examples of dates + times, price values etc where you believe data to be missing.
0
Answers
-
Hello @hamza.khalid
You may enable the RFA trace file to check if the API receives the QUOTIM_MS field from the your server (if that field is updated).
You can enable the RFA RSSL trace with the following paremters:
\Connections\<ConnectionName>\traceMsgToFile = true
\Connections\<ConnectionName>\traceMsgDomains = "all"
\Connections\<ConnectionName>\traceMsgMaxMsgSize = 5000000
\Connections\<ConnectionName>\traceMsgMultipleFiles = true
\Connections\<ConnectionName>\tracePing = true0 -
Hi, So in the update messages if I don't receive timestamp, does is it mean that the Timestamp is the same as it was in the previously received message of that particular Symbol. For example :
First update Message : BidPrice 12.00, BidSize: 3000, QUOTIM_MS: 3456700
Second update Message : BidPrice 12.50, BidSize: 1000
Now, there was no QUOTIM_MS in the second message, does that mean for the second BID event the QUOTIM_MS is the same as the first because the definition of 'update messages' promise to send only those attributes which are changed.
0 -
I am not a content expert so cannot provide definitive advice on the scenario described above. However, if I received the 2nd update without a timestamp field I would assume the previous timestamp still applied. However, if this did not make sense based on the fields present in the 2nd update, I would query with a Content specialist via MyRefinitiv as described as above.
As you are using a view it may be possible that the timestamp is in a different field for the 2nd update but is being filtered out by the server due to your View request. Again the Content specialist could advise on this.
I would also enable the Trace as described by my colleague and confirm which fields are definitely being received on the wire from the server - i.e. just to be sure it is not an application-level issue.
0 -
Also, one more thing sometimes I only receive BIDSIZE in the update message without any BIDPrice, does that mean the new price is same as the price of the previous Bid event of a particular instrument?
I have tried using the configs that your colleague has suggested and it seems that it is not an application level issue.
0 -
As mentioned, I am not a content expert - most of us on these forums are on the API side - that is why we recommend you raise content queries with the content helpdesk.
Logically speaking, if you receive only a BIDSIZE in an update then yes it would indicate that only the number of orders has changed but the BID Price remains the same.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛