I am consistently receiving the following timeout error when trying to run a backtest:
Start New Discussion 
Back
Reward Discussion 
Algorithm.Initialize() Error: Execution Security Error: Operation timed out - 0.25 minutes max.Is there a way to increase the timeout threshold?
I really like this platform, but more often than not I receive this error and it is making it hard to use.
The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.
Experiencing same behavior with this algo as well
Thanks Caleb we'll look into increasing it. That part of the code should take about 0.5s, its very strange its taking 15s. We're at higher than ever backtesting loads so it might just be some growing pains.
The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.
Thanks Jared!
The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.
Thanks again Jared. Haven't got a timeout in a few days.
The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.
I think I got it figured out. In case anyone else is still stuck with this timeout, I'm pretty sure that I had used the Schedule.On() helper with a callback function that was much too large. Instead, I used a flag to trigger the function and that worked properly. It was failing before it gave me a deploy ID, so I couldn't send that to support. Thanks for the help anyway :)
7
if self.output.scheduleAnalysisFlag == False and self.output.warmupLeft <= self.output.analysisWarmup:
if self.settings.analysisInterval == 'Monthly':
self.Schedule.On(self.DateRules.MonthStart(), self.TimeRules.At(10,0), self.initializeScheduler)
elif self.settings.analysisInterval == 'Weekly':
self.Schedule.On(self.DateRules.WeekStart(), self.TimeRules.At(10,0), self.initializeScheduler)
elif self.settings.analysisInterval == 'Daily':
self.Schedule.On(self.DateRules.EveryDay(), self.TimeRules.At(10,0), self.initializeScheduler)
self.output.scheduleAnalysisFlag = True
# sets the runAnalysisFlag to true.
def initializeScheduler(self):
self.output.runAnalysisFlag = TrueThe material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.
To unlock posting to the community forums please complete at least 30% of Boot Camp.
You can
continue your Boot Camp training progress from the terminal. We
hope to see you in the community soon!
QuantConnect™ 2023. All Rights Reserved
|