Curr time: 12/4/2024 @ 9:35:13 IssueShortatMarket {
“ok” : “0”,
“signal” : {
“symbol” : null
},
“error” : {
“title” : “Signal Not Accepted”,
“message” : “Expired future or invalid symbol format. Please see Collective2 Future Symbols - Collective2”
},
“elapsed_time” : “0.0051”
}
I got the above today trying to short NQ. am almost certain it is not an issue on my side (i.e symbol was sent correctly, I dont have proof for it, but i have not touched my set up for years and problem seemed to be visible only on one system)- any thing changed/ not working on your side @MatthewKlein ? anyone else had issues? this was around 9:35:13 est on system id 147358434. the short signal was sent 5 times with 5 second intervals and all of them failed. i can also see orders went through around this time on my other systems
1 Like
Yes, I posted an alert on the site about this. I should have also done so here. There was indeed a colossal problem … all symbols were described as invalid.
This is now fixed.
Sorry!
2 Likes
Thanks for update @MatthewKlein
1 Like
yet another API error today on systemid 128871252 although a different reason -
Curr time: 3/5/2024 @ 10:1:21 IssueBuyatMarket {
“ok” : “0”,
“signal” : {
“symbol” : null
},
“errorCode” : “marginViolation”,
“errorNumber” : 300,
“error” : {
“title” : “Unable to place trade due to margin constraints”,
“message” : “Unable to BTO 1 @NQM4 - Current account buying power is ($177,362.00), cash is $199,536.00; equity=($352,528.00); currMarginUsed=$24,370.00; proposed trade would lower by $26,807.00 (C2 Err Code: PreMarginCheck api2 a)”
},
“elapsed_time” : “7.8864”
}
System was trying to buy a second NQ contract. Model account is big enough to hold 2 contracts. I assuume there was another glitch? @MatthewKlein , any idea?
is there an issue with API today? Anyone experiencing issues?
@MatthewKlein - it seems getsystemdetails endpoint is returning strange characters. As a result none of programs went beyond the line of code where the result of the call was logged. see below in bold( there is plent of more strange characters in the complete response ). was this api touched over the weekend?
{
“ok” : “1”,
“response” : {
“longDescription” : “system trade many subsystems - 5 subsystems day trading 1 NQ each, 1 subsystem trading 20 MNQ on short side (equivalent to 2 NQ) . The only overnight exposure comes from 1 subsystem that trades 1 NQ short term \n\nUpdate Jan 2022 → system rescaled to 70% (hence you will see fractional contracts on trade details. Position sizing remains the same going forward though - max 5 contract intraday , max 1 NQ overnight) → In hindsight, this was bad timing! Got the worst drawdown right after the rescale, trading same number of contract. And as a result, max drawdown in percent terms got bigger and looks more than what I would have liked to.\n\nUpdate July 2022 → system rescaled to 80% (hence you will see fractional contracts on trade details. Position sizing remains the same going forward though - max 5 contract intraday , max 1 NQ overnight)\n\nUpdate Mar 2023 → model account rescaled to 65% ( 170k to 110k)”,
“system_id” : “129875048”,
“statistics” : {
“x?x?x?xÝx› xcx? xx"x?x?x"x?x?x?” : {
“metainfo” : {
“bunch” : “Statistics related to linear regression on benchmark”,
“dataset” : “Analysis based on DAILY values, last 6 months only”,
“group” : “RATIO STATISTICS”,
“suffix” : null,
“category” : “Ratio statistics of excess log return rates”,
“helpText” : null,
“precision” : “5”,
“prefix” : null,
“multiplier” : “1.000000”
},
“value” : “0.46844”
OK, I think this is fixed. Issue was we recently added new language support, and the API was incorrectly returning Hebrew characters, which broke our JSON. Please try again and let me know if you agree it is fixed.
yes, seems fine now. Thanks. I hope no other api end point is affected by this
hi @MatthewKlein , was there any issue around 1415EST wrt API ? My logs say getSystemDetails failed for few of my systems at the same time. It failed 5 times consecutively. The next attempt after 5 minutes was fine
