Can the Status Text response from from NIP be changed

Is it possible to the same text status for NIPs as we do for IPs? For Non-existent Items we get the following response:
Received CLOSED msg for RIC [invalidItem]. This RIC is closed.
[Wed Jan 22 14:12:40.898] Closed Status Received. Item:<invalidItem> (Text: "F10: Not In Cache")
The Subscribing application will then retry, as there can be many subscribing apps, this can put unnecessary load on the NIP
On an Interactive feed for non-existent items the status is:
Received CLOSED msg for RIC [invalidItem]. This RIC is closed.
[Wed Jan 22 14:21:46.050] Closed Status Received. Item:<invalidItem> (Text: "The record could not be found")
Is it possible to ge the "Record could not be found" text status or is this a limitation with how NIPs work?
Best Answer
-
One further point, it is generally not advisable for application to act on the contents of the text message - as these could change over time - potentially causing issues with the application.
It is upto the consumer to not retry 'CLOSED' status items unless they are almost certain the situation is transient and the RIC should be available momentarily.
0
Answers
-
Hi @julian.octave As you are aware, the items published by NIP are cached by the TREP infrastructure - which handles sending image/updates and status messages to subscribers, vs IP which handles all the subscription requests, caching and generates its own status message.
The NIP text is coming from TREP, which does not have the item in cache. This message can not be changed.
0 -
@anton.goldenfarb - Got these Answers, just wanted to loop you in
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛