Incorrect CONTR_MNTH RIC Values

Hi,
I subscribe to the chain RIC 0#/NGLN: and the field CONTR_MNTH.
We use the ezd tool together with code written in .NET to subscribe to these RICS using RFA and a subset of fields.
I noticed that occasionaly we seem to be getting wrong CONTR_MNTH values for some of the chain constituent RICs.

RIC Capture Time CONTR_MNTH

/NGLNMF9 22/12/2018 01:28 JAN9

/NGLNMF9 23/12/2018 01:28 JAN9

/NGLNMH2 23/12/2018 23:58 JAN9

/NGLNMF9 24/12/2018 00:03 JAN9

/NGLNMF9 24/12/2018 01:28 JAN9

/NGLNMF9 25/12/2018 01:28 JAN9

/NGLNMF9 26/12/2018 01:33 JAN9

/NGLNMF9 27/12/2018 01:45 JAN9

/NGLNMF9 28/12/2018 01:34 JAN9

/NGLNMQ5 28/12/2018 23:50 JAN9

As you can see there are 3 RICs where the CONTR_MNTH is the same all captured at different times:
/NGLNMF9
/NGLNMH2
/NGLNMQ5

Have you got any idea why this is happening?
Thanks

Find more posts tagged with

trep

rfa

rfa-api

Accepted answers

All comments

zoya faberov

Hello @emir.subasic,

Thanks for reporting this.

For content questions, issue reports, verification requests, the best and most efficient way to get answers is to contact Refinitv content experts via Content Helpdesk, either by submitting it online via My TRSupport -> " I need help with content" -> Elektron Realtime or to call your local TR Helpdesk.

This forum is dedicated to API-related questions.

In this instance I have opened the support inquiry on your behalf, support case # is 07263900.

JoseEmmanuel.DeLeon

Hi @zoya faberov,

Client @emir.subasic, has contacted helpdesk case 07259676, And we are able to confirm with the Content team that we do not issue regarding the Data. However client is seeing different value for /NGLNMH2 23/12/2018 23:58 JAN9, (instead of AUG5)

/NGLNMQ5 28/12/2018 23:50 JAN9 (instead of MAR2). Please the see the attached files. nglnmq5-2.png nglnmh2-2.png. Since client is using RFA .NET can you please confirm if could be some issue on your infrastructure?

zoya faberov

Hello @emir.subasic and @JoseEmmanuel.DeLeon

The content supplied via Elektron service, and accessible via EZD or other connection means is the same, and should not depend on the API you access it with.

Our content services confirm that there no outage or data issue on that day.

I have just retrieved the corresponding history from our history TRTH, for RIC NGLNMH2, for Dec 23, and the value of CONTR_MONTH is "MAR2"

Please confirm if via your custom RFA.NET app you continue seeing JAN9 for /NGLNMH2 ?

zoya faberov

@emir.subasic @JoseEmmanuel.DeLeon,

I have just additionally tested "/NGLNMH2" over EZD, I am seeing "MAR2" in fid 41.

So please confirm what value are you currently seeing in your custom RFA.NET app in fid 41?

Additionally, I am noting, that fid 41 updates very seldom. Consequently, if any if the updates are missed or not processed by the consumer app, the consumer will end up showing the old value, consistent with what you are observing. Have you had a chance to review the app logs for the specified dates?

EXPLORE OUR SITES