row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission

Can you please help us to understand what this error means? Our daily process runs fine but one day we saw these errors repeating for many RICs for which We are downloading TRTH intraday price summary. The details are as below -
WH0 : Request failed = {"@odata.context":"https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#RawExtractionResults/$entity","JobId":"0x06439435ab9b3026","Notes":["Extraction Services Version 12.1.39202 (f3a5974597fc), Built Jul 18 2018 22:27:40\nUser ID: 9014963\nExtraction ID: 2000000035448367\nSchedule: 0x06439435ab9b3026 (ID = 0x0000000000000000)\nInput List (15 items): (ID = 0x06439435ab9b3026) Created: 07/23/2018 05:49:38 Last Modified: 07/23/2018 05:49:38\nReport Template (16 fields): _OnD_0x06439435ab9b3026 (ID = 0x06439435af5b3026) Created: 07/23/2018 05:49:18 Last Modified: 07/23/2018 05:49:18\nSchedule dispatched via message queue (0x06439435ab9b3026)\nSchedule Time: 07/23/2018 05:49:20\nProcessing started at 07/23/2018 05:49:20\nProcessing completed successfully at 07/23/2018 05:49:38\nExtraction finished at 07/23/2018 05:49:38 UTC, wit! h servers: x04q13\nInstrument expanded to 1 RIC: WH0.\nInstrument expanded to 1 RIC: WH1.\nInstrument expanded to 1 RIC: WH9.\nInstrument expanded to 1 RIC: WK0.\nInstrument expanded to 1 RIC: WK1.\nInstrument expanded to 1 RIC: WK9.\nInstrument expanded to 1 RIC: WN0.\nInstrument expanded to 1 RIC: WN1.\nInstrument expanded to 1 RIC: WN9.\nInstrument expanded to 1 RIC: WU0.\nInstrument expanded to 1 RIC: WU8.\nInstrument expanded to 1 RIC: WU9.\nInstrument expanded to 1 RIC: WZ0.\nInstrument expanded to 1 RIC: WZ8.\nInstrument expanded to 1 RIC: WZ9.\nTotal instruments after instrument expansion = 15\n(RIC,WH0,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WH1,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,W! H9,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WK0,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WK1,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WK9,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WN0,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WN1,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WN9,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WU0,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WU8,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WU9,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD)! , CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WZ0,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WZ8,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\n(RIC,WZ9,CBT) row suppressed for lack of 'CBT-WB (CBOT-WALLBOARD), CBT (CHICAGO BOARD OF TRADE)' permission.\nReport suppressed because no instruments are permitted\n"]}
Best Answer
-
Further update from support:
"... we have found that there was an Alert raised on 23/07/2018 (around the same time the
client did the extraction) that was resolved as per below:-
Resolved
SERVICE ALERTS
Subject: DataScope Select - Data for Certain
Instruments - Was Unavailable
Issue Description:
Some users were unable to access selected data on DataScope Select GUI and
Extractions until 08:40 GMT.
This was due to a permissioning issue at Thomson Reuters.
Customers globally were affected by this incident.
The major incident management process was invoked at Thomson Reuters to aid
service restoration.
Status at 09:01 GMT: The services were restored at 08:40 GMT.Alert ID 176443 Alert Status Resolved First Reported 23-July-2018
06:20 GMTOutage Start 23-July-2018
00:00 GMTActual
Resolution23-July-2018
08:40 GMT"
Please confirm that you are not currently seeing this, it has been resolved.
Thanks,
-AHS
0
Answers
-
Hello @rahul_srivastava,
Please include the complete request that has caused this error.
I have understood, that your daily extraction process has been running this extraction request successfully, no permission errors were reported, and only this specific run of that same request has failed with "lack of CBT ... permissions",
I have created support case# 06775422 to properly investigate this incident. We will need to add the request information to it.
In the future, if you are observing an issue, rather then have a question, it will be more efficient to open a support incident directly via myaccount.thomsonreuters.com.
0 -
From support :
"... the client has no permission to extract
the values for CHICAGO BOARD OF TRADE hence the error arises as row
suppressed due to lack of permission.To discuss adding the required
permissions, please contact your Thomson Reuters account manager ..."0 -
This is the request body -
Request Body : OrderedDict([('ExtractionRequest', OrderedDict([('@odata.type', '#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryIntradaySummariesExtractionRequest'), ('ContentFieldNames', ['Open', 'High', 'Low', 'Last', 'Volume', 'No. Trades', 'Open Bid', 'High Bid', 'Low Bid', 'Close Ask', 'Close Bid', 'High Ask', 'Low Ask', 'No. Asks', 'No. Bids', 'Open Ask']), ('Condition', OrderedDict([('MessageTimeStampIn', 'GmtUtc'), ('ReportDateRangeType', 'Range'), ('QueryStartDate', '2018-07-20T00:00:00.000-05:00'), ('QueryEndDate', '2018-07-20T23:59:59.999-05:00'), ('SummaryInterval', 'OneMinute'), ('TimebarPersistence', 'true'), ('DisplaySourceRIC', 'true')])), ('IdentifierList', OrderedDict([('@odata.type', '#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList'), ('InstrumentIdentifiers', [{'Identifier': 'WH0', 'IdentifierType': 'Ric'}, {'Identifier': 'WH1', 'IdentifierType': 'Ric'}, {'Identifier': 'WH9', 'IdentifierType': 'Ric'}, {'Identifier': 'WK0', 'IdentifierType': 'Ric'}, {'Identifier': 'WK1', 'IdentifierType': 'Ric'}, {'Identifier': 'WK9', 'IdentifierType': 'Ric'}, {'Identifier': 'WN0', 'IdentifierType': 'Ric'}, {'Identifier': 'WN1', 'IdentifierType': 'Ric'}, {'Identifier': 'WN9', 'IdentifierType': 'Ric'}, {'Identifier': 'WU0', 'IdentifierType': 'Ric'}, {'Identifier': 'WU8', 'IdentifierType': 'Ric'}, {'Identifier': 'WU9', 'IdentifierType': 'Ric'}, {'Identifier': 'WZ0', 'IdentifierType': 'Ric'}, {'Identifier': 'WZ8', 'IdentifierType': 'Ric'}, {'Identifier': 'WZ9', 'IdentifierType': 'Ric'}]), ('UseUserPreferencesForValidationOptions', 'false')]))]))])
Please note that every day we are running the extraction for same RIC and it works fine. The problem happened only for
('QueryStartDate', '2018-07-20T00:00:00.000-05:00'), ('QueryEndDate', '2018-07-20T23:59:59.999-05:00'),
And when we reran the process for same date, it again worked fine. It just failed in one occasion.
The user detail is as follows -
'UserId': 9014963, 'UserName': 'SSGA TRTHbatch'
0 -
@rahul_srivastava, as an added comment:
For the support team to investigate a specific query, the user name is insufficient. It requires a unique Client-Session-Id, specific to that query (i.e. each query you make should have a different and unique one), and the Request-Execution-Correlation-Id which the server returns to you. For details on these Ids, see here: https://hosted.datascopeapi.reuters.com/RestApi.Help/Home/Diagnostics
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
- 689 Datastream
- 1.4K DSS
- 625 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 558 WebSocket API
- 39 FX Venues
- 15 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
- 277 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 1.9K Refinitiv Data Platform
- 695 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 93 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛