Possible issues with interactive brokers manual positions

Based on the information provided in the extracts, it seems like the error "Object reference not set to an instance of an object" typically occurs when you're trying to access a property or method on an object that hasn't been initialized yet.

In your case, it seems like the error is occurring when the algorithm is trying to get open orders from the brokerage. This could potentially be due to the manually opened short position via the Interactive Brokers interface.

However, without more specific information about your code and the exact circumstances under which the error occurs, it's hard to provide a definitive solution.

One of the users in the forum discussions suggested initializing properties in the __init__ method of your class to avoid this error. Here's how you can do it in Python:

class YourAlgorithm(QCAlgorithm):
    def __init__(self):
        self.asset = None
        self.price = None
        # Initialize other properties...

Now, when you try to access these properties in your algorithm, they will have been initialized and you shouldn't get the "object reference not set up" error.

If the issue persists, it would be best to submit a support request to QuantConnect with the algorithm attached for more assistance.

Please note that this advice is based on the information available in the extracts and might not completely solve your issue.

Sources:

• Forum Discussion 15883
• Forum Discussion 10999

The problem occurs even with the most basic QCalgorithm without any trading logic. As soon as qc attempts to sync with the brokerage the error occurs. Again, this has only happened since I ‘manually’ opened a short position via the IB interface, and I had to redeploy.

Based on the information provided in the extracts, it seems like the error "Object reference not set to an instance of an object" typically occurs when you're trying to access a property or method on an object that hasn't been initialized yet.

In your case, it seems like the error is occurring when QuantConnect attempts to sync with the brokerage. This could potentially be due to the manually opened short position via the Interactive Brokers interface.

However, without more specific information about your code and the exact circumstances under which the error occurs, it's hard to provide a definitive solution.

If the issue persists, it would be best to submit a support request to QuantConnect with the algorithm attached for more assistance.

Please note that this advice is based on the information available in the extracts and might not completely solve your issue.

Sources:

• Forum Discussion 15883
• Forum Discussion 10999

I got the same error as well. Just tried and still having the issue even for an algo that doesn't do anything. 

My positions are not manual trades so it probably doesn't matter.

The lean version is showing “master v16027 2023-11-17 20:13” and I wanted to test with earlier version of lean but the drop down doesn't show other version selection. Searching for ways to go to earlier lean, short of setting up local.

Indeed I tried the same thing with a very simple algo and got the same issue.

Made me wonder if there was some problem with symbols not lining up between IB and QC.

Thankfully I only have one position open and I don't stand much to lose by closing it. Will post again as soon as I can test the deployment with the position closed.

I can confirm that closing the position on IB enabled me to ‘go live’ successfully with the algorithm.

Thus the issue does indeed seem to be synchronisation of IB with QC. If anyone has any details about how to handle this, it would be appreciated, as this is quite a serious issue that currently prevents me (and I imagine, others like Swiftmox) from relaunching the algo when there are open positions.

Hello Matthew Vowels 

Thank you for the report, and sorry for the inconvenience. We've identified the issue and disabled the bugged version.