If a backtest result has been embedded in the docs for a long time, it can start to produce errors when it runs. There isn't currently a script that periodically checks if the backtests run error-free.
Checklist
[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
Expected Behavior
All of the embedded backtest results in the docs run error-free when you clone and run them in QC Cloud. There is a "link checker"-style script that clones all of the embedded backtests in the docs (ex: https://www.quantconnect.com/terminal/clone/19206959/30daece11812d8fcc8d2fa92451c3ce5/clone-of%3A-clone-of-clone-of-determined-fluorescent-yellow-rhinoceros) and uses the QC API to backtest them and check for errors.
Actual Behavior
If a backtest result has been embedded in the docs for a long time, it can start to produce errors when it runs. There isn't currently a script that periodically checks if the backtests run error-free.
Checklist
masterbranch