Tick History Cash quota exceeded

Options
nicola.donelli
nicola.donelli Newcomer
in TRTH

I am performing an ElektronTimeseriesExtractionRequest for RIC "EURJPY=" but I got this output (and not content)


Extraction Services Version 14.3.41935 (052f652420ba), Built Oct 12 2020 20:12:34
Processing started at 2020-11-06 16:49:54.
User ID: 9026587
Extraction ID: 2000000195692253
Schedule: 0x0750f95ba6170637 (ID = 0x0000000000000000)
Input List (1 items):  (ID = 0x0750f95ba6170637) Created: 2020-11-06 16:49:54 Last Modified: 2020-11-06 16:49:54
Report Template (10 fields): _OnD_0x0750f95ba6170637 (ID = 0x0750f95ba6370637) Created: 2020-11-06 16:49:52 Last Modified: 2020-11-06 16:49:52
Schedule dispatched via message queue (0x0750f95ba6170637)
Schedule Time: 2020-11-06 16:49:53
Timeseries Date Range: 2020-10-01 to 2020-10-30
Processing completed successfully at 2020-11-06 16:49:54, taking 0.224 Secs.
Extraction finished at 2020-11-06 15:49:54 UTC, with servers: x01q14, ETS (0.1 secs), QSHC15 (0.0 secs), QSSHA1 (0.0 secs)
Quota Message: INFO: Tick History Cash Quota Count Before Extraction: 15; Instruments Approved for Extraction: 0; Tick History Cash Quota Count After Extraction: 15, 100% of Limit; Tick History Cash Quota Limit: 15
Quota Message: ERROR: The RIC 'EURJPY=' in the request would exceed your quota limits. Adjust your input list to continue.
Quota Message: WARNING: Tick History Cash Quota has been reached or exceeded
Writing RIC maintenance report.

What does it mean that I exceeded my Tick History Cash quota limit?

And how could I keep my Tick History Cash quota limit under control to avoid this in the future?


Thanks

Tagged:

Best Answer

  • zoya faberov
    zoya faberov ✭✭✭✭✭
    Answer ✓

    Hello @nicola.donelli,

    Looks like you have exceeded the requests Quota that is allocated to your DSS ID.

    Pease look it up via DSS GUI:

    image

    I would keep it under control proactively, by planning the number of requests issued to be under the quota assigned.

    An alternative approach is to run API quota request

    {{protocol}}{{host}}{{api}}/Quota/GetQuotaInformation

    periodically, and examine the results.

    And/or to always examine any error that is received (as you just did) and to look out for the error on quota exceeded.

Answers

Categories