Download open orders on connection helps expose order details when an API client connects. Review it with the app’s startup behavior. Receiving an order record does not automatically grant the client permission to change that order.
Educational software guidance. Trading involves risk. Read the financial and information disclaimers.
Step by step
- 1 Open Global Configuration → API → Settings.
- 2 Locate Download open orders on connection and record its current state.
- 3 Compare the setting with the app’s documented startup requirements.
- 4 After a controlled reconnect, compare the app’s order view with TWS working orders.
- 5 If orders are missing, check client scope and binding behavior with the app provider.
A practical example
An app starts after an order was already placed. It needs to learn what is working so it does not act on an empty view. Check whether its startup flow receives the expected order list. But keep two questions separate: can it see the order, and can it change the order? The first does not prove the second. Ask the app provider about its client scope if the list is incomplete.
Screen reference
Start in Mosaic with File → Global Configuration. Then choose the panel named in the steps.


Mistake to avoid
Common questions
Does this place new orders?
It concerns order details on connection, not a new trading instruction.
Is viewing the same as changing?
No. Ownership and binding rules can still restrict changes.