This problem already occurred earlier this week.
Runtime Error: Algorithm took longer than 10 minutes on a single time loop. CurrentTimeStepElapsed: 10.1 minutes in Isolator.cs:line 1792024-06-19 15:44:56 :Don't have an account? Join QuantConnect Today
QuantConnect Community Discussions
QUANTCONNECT COMMUNITY
LEAN is the open-source algorithmic trading engine powering QuantConnect. Founded in 2012 LEAN has been built by a global community of 180+ engineers and powers more than 300+ hedge funds today.
Join QuantConnect's Discord server for real-time support, where a vibrant community of traders and developers awaits to help you with any of your QuantConnect needs.
The Open-Quant League is a quarterly competition between universities and investment clubs for the best-performing strategy. The previous quarter's code is open-sourced, and competitors must adapt to survive.
Refer to our Research Guidelines for high quality research posts.
Create an account on QuantConnect for the latest community delivered to your inbox.
Sign Up Today
|
|
|||||||
|
|
||||||||
|
Live servers crash again. Is there still a problem on your end?
Amir Goren | June 2024
This problem already occurred earlier this week.
Runtime Error: Algorithm took longer than 10 minutes on a single time loop. CurrentTimeStepElapsed: 10.1 minutes in Isolator.cs:line 1792024-06-19 15:44:56 :QuantConnectâ„¢ 2025. All Rights Reserved
Mia Alissi
The error "Algorithm took longer than 10 minutes on a single time loop" typically occurs when your algorithm is performing a task that is too computationally intensive, causing it to exceed the time limit set by QuantConnect's LEAN engine.
There are several potential causes for this error. It could be due to a large number of calls to the History method, a large History call inside a universe selection function, or a computationally intensive task such as training a machine learning model.
Here are some suggestions to resolve this issue:
Reduce the number of calls to the History method. This method is computationally expensive, especially when called with a large number of symbols or a long time period.
If you're using a universe selection function, try to optimize it. For example, in one of the discussions, a user was advised to replace the universe with a ManualUniverseSelectionModel and remove redundant code.
If you're training a machine learning model, consider reducing the complexity of the model or the size of the training data.
Here's an example of how you can optimize a universe selection function in Python:
Remember, these are just suggestions. The exact solution will depend on the specifics of your algorithm.
Sources:
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.
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!