You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the data connection is lost, LEAN recovers it. No need to restart the deployment.
Actual Behavior
Apparently the algorithm trading SPX options fails because the algorithm stops receiving SPX (index data), so it didn't trigger the option universe filter.
The latest "Market data farm connection" says
2023-08-08T05:07:28.4818118Z TRACE:: InteractiveBrokersBrokerage.HandleError(): RequestId: -1 ErrorCode: 2108 - Market data farm connection is inactive but should be available upon demand.usopt
but it refers to usopt, not index.
When the user restarted the algorithm, it received the data.
Potential Solution
N/A
Checklist
I have completely filled out this template
I have confirmed that this issue exists on the current master branch
I have confirmed that this is not a duplicate issue by searching issues
I have provided detailed steps to reproduce the issue
The text was updated successfully, but these errors were encountered:
for data connection if there are no subscriptions:
2024-08-11T22:11:27.0548386Z TRACE:: CompositeDataQueueHandler.SetJob(): will use ["QuantConnect.DataDistribution.Common.LocalDataDistributionConsumer"]
...
2024-08-11T23:50:56.5941827Z TRACE:: InteractiveBrokersBrokerage.HandleError(): RequestId: -1 ErrorCode: 2157 - Sec-def data farm connection is broken:secdefnj
2024-08-11T23:51:08.7178800Z TRACE:: InteractiveBrokersBrokerage.StartGatewayRestartTask(): triggering soft restart
Expected Behavior
If the data connection is lost, LEAN recovers it. No need to restart the deployment.
Actual Behavior
Apparently the algorithm trading SPX options fails because the algorithm stops receiving SPX (index data), so it didn't trigger the option universe filter.
The latest "Market data farm connection" says
but it refers to usopt, not index.
When the user restarted the algorithm, it received the data.
Potential Solution
N/A
Checklist
master
branchThe text was updated successfully, but these errors were encountered: