I got this fault when running a sim.
It's the same issue as this: Request failed: Failed to receive message header
The cause is that it takes too long to process before transmitting the next progress message, so the request system presumes the request is stuck and allows the user to make more requests. But the simulation continues to run on the server after the Request failed: Timeout waiting for message error, so it is not safe to retry.
As mentioned on the other thread, you can work around it by removing the 3 unused AIFactor() nodes from your ranking system.
Your simulations does run to the end , but it's taking 20 min , and it's causing a timeout in some of the inter process communications.
The strict timeouts that we put in place made sense for ranking , but not for predictions. We are going to increase the timeouts as a quick fix. We should have this out by tomorrow.
You'll still have to wait 20 min for your backtest, but it should work. We will look for a better engineered solution to reduce the backtest time dramatically. Also, you should still remove unnecessary AIFactor() from the ranking system until we have the fix in place that ignores 0 weighted AIFactors().
Thanks
1 Like