MasterTableUpdate Error Events in NT Log

[Lancer]

In the NT log (trace files), I am seeing over 10 events per hour of this:

ERROR [2023-01-20 14:43:05,714] - Can't apply MasterTableUpdate for F.US.CLE.G23 because there is no InstrumentState. MT is <ContractMTData:base=<MTUpdateBase:InstrumentId= 25 511424,UtcDateTime="2023-01-20 14:43:05.640",TradingDate="0001-01-01 00:00:00.000",DayOffset=Today>,IndicativeOpenStatu s="Expired">. Is Subscribed: False
ERROR [2023-01-20 14:43:56,197] - Can't apply MasterTableUpdate for F.US.CLE.G23 because there is no InstrumentState. MT is <ContractMTData:base=<MTUpdateBase:InstrumentId= 25 511424,UtcDateTime="2023-01-20 14:43:56.152",TradingDate="0001-01-01 00:00:00.000",DayOffset=Today>,IndicativeOpenStatu s="Expired">. Is Subscribed: False
ERROR [2023-01-20 14:50:08,110] - Can't apply MasterTableUpdate for F.US.CLE.G23 because there is no InstrumentState. MT is <ContractMTData:base=<MTUpdateBase:InstrumentId= 25 511424,UtcDateTime="2023-01-20 14:50:08.060",TradingDate="0001-01-01 00:00:00.000",DayOffset=Today>,IndicativeOpenStatu s="Expired">. Is Subscribed: False
ERROR [2023-01-20 14:51:20,972] - Can't apply MasterTableUpdate for F.US.CLE.G23 because there is no InstrumentState. MT is <ContractMTData:base=<MTUpdateBase:InstrumentId= 25 511424,UtcDateTime="2023-01-20 14:51:20.908",TradingDate="0001-01-01 00:00:00.000",DayOffset=Today>,IndicativeOpenStatu s="Expired">. Is Subscribed: False

G23 appears to be referring to a February 2023 contract, but can't decipher the instrument. How do I fix this?

[NinjaTrader_SeanH]

Hello Lancer,

Thank you for your post.

The CLE is referring to Crude oil CL. It appears the instrument needs to be rolled over to the next expiry. Crude Oil is now trading with the 03-23 expiry.

[Lancer]

I rolled CL to March after the regular session on the 17th, so that's not it. Tools > Database Management > Rollover futures instruments shows nothing to roll. Any other ideas?

[NinjaTrader_SeanH]

Hello Lancer,

Thank you for replying.

Please reach out to [email protected] and submit a ticket for this matter.