API error today

C2
1

Hi @MatthewKlein
I experienced errors today as below. Have not seen this error, definitely not in the recent past. Anything to be concerned?

Curr time: 8/7/2022 @ 11:50:22 IssueSellatMarket {
“errorNumber” : 202,
“lastatcreate” : “”,
“elapsed_time” : “10.0514”,
“ok” : “0”,
“signal” : {
“symbol” : null
},
“errorCode” : “noBid”,
“error” : {
“title” : “Market Order Not Accepted”,
“message” : “No bid for this instrument. Market order not accepted.”
}
}

Curr time: 8/7/2022 @ 11:50:22 MainScript Processed signal failed attempt 0
Curr time: 8/7/2022 @ 11:50:33 IssueSellatMarket {
“ok” : “1”,
“signal” : {
“minTick” : “0.25”,
“market” : “1”,
“strike” : null,
“signalid” : “141005299”,
“stoploss” : “”,
“comments” : null,
“receivedWhenUnixTime” : 1657295433,
“day” : “1”,
“systemid” : “129875048”,
“parkUntilYYYYMMDDHHMM” : null,
“symbol” : “@NQU2”,
“conditionalupon” : null,
“duration” : “DAY”,
“description” : “E-MINI NASDAQ 100 STK IDX [CME Chicago Mercantile Exchange]”,
“targetocagroupid” : null,
“decimalprecision” : “2”,
“receivedWhenET” : “2022-07-08 11:50:33”,
“expiresat” : 1657314000,
“pointvalue” : “20”,
“parkUntilSecs” : null,
“typeofsymbol” : “future”,
“currency” : “USD”,
“limit” : 0,
“quant” : “1”,
“gtc” : “0”,
“stop” : “0”,
“profittarget” : “”,
“action” : “STC”,
“ocaid” : null
},
“signalid” : “141005299”,
“elapsed_time” : “5.3483”
}

The second attempt did go through. was there any update on API on your side? @MatthewKlein

Thanks

2

Our data provider went down sporadically through the day. We’re fixing all associated data errors. I apologize for the problem.

3

Thanks for the update @MatthewKlein

4

today I got an error from API that I have not seen before. logs shows the below response for every attempt to sell MES at market (system - MES Trader (collective2.com))

Curr time: 19/7/2023 @ 14:0:23 IssueSellatMarket

Just a moment...
Enable JavaScript and cookies to continue

Curr time: 19/7/2023 @ 14:0:23 IssueSellatMarket exception at issue sell

Any idea why this showed up for first time after more than 3 years of API usage?

I had several other orders today that did not have this problem

Thanks in advance