At the moment, as far as I understand it, when re-connecting a broker plugin has the option of accepting the last known state from RightEdge (regardless of the state of orders/positions at the broker) or to update the state of orders/positions within RightEdge. The problem with the latter option, as I understand it, is that RightEdge will no longer actively manage those positions. ie, it won't submit stops or profit targets for them or automatically cancel them after X bars which may come as a surprise to the trader who is expecting RightEdge to automatically do this. Could the syncing api be improved somehow so that the RightEdge could be updated with the state at the broker during a re-connect and RightEdge could then continue to manage all the resultant orders/positions as per normal?

I'd really like the ability to submit stop-loss and profit-target orders to the broker along side the initial market/limit order. ie, submit an If / Then OCO order to the broker so that if the market/limit order is filled, the stop/proft orders are automatically activated and the execution of one cancels the other - all done by the broker. Many brokers support this type of order and for those that don't the existing process within RE simulates it easily enough and would be backwards compatible. However, for those brokers that can support it, it reduces the risk of losing money in the event of a network disconnect or system crash because the stops/profit targets are automatically lodged with the broker along-side the initial order. At the moment, there is a risk that a limit order could be hit but network problems, etc could prevent RightEdge from submitting the stop-loss or profit orders.

Hopefully some of us are already or will soon be leaving our systems automatically running for weeks and months. When trading equity indexes (ASX200, FTSE200) stocks get added and removed from these indexes periodically. It would be nice to have the ability to update a symbol list and trading strategy with the new symbols and tell a strategy that an old symbol has been removed (so that it can stop monitoring it and/or close any open positions in the symbol). At the moment, the only way to do this is to monitor a larger universe of stocks and to source the data externally into the trading strategy so that it can only place trades in the correct constituents. This could work but could increase memory usage significantly because indicators would have to be calculated for the larger universe and hence more memory would be required to accommodate all the extra data + indicators. Also additional bandwidth would be required to monitor the larger universe. Probably workable but perhaps not ideal.

It would be nice to be able to update a limit order (or stop-loss or profit-target order) without first having to cancel the old one and then submit a new one. At the moment there is a window of time when no limit order exists at the broker (after the old one has been cancelled and before the new one has been submitted). Many brokers now support the ability to update a limit order with new values to reduce this risk. It sounds like it may be possible to support this in a backwards compatible manner (similar to the one above). ie, if the broker can update a limit order, then great; if not, default to the current behaviour of cancellation and re-creation.

RightEdge store the active state of all orders and positions in an XML file and then uses this when re-starting to manage previously submitted orders and fills. I encountered a problem where this file became corrupt and hence RightEdge wasn't able to restart. Is it possible that a backup of file could be stored somewhere and RightEdge could automatically fallback to the backup if the main one becomes corrupt? Or could all writes to the file be made synchronously so that the risk of corruption is reduced? Or else, if the file is corrupt, perhaps log an error somewhere, remove the old file, and continue. This would allow a system to automatically restart without needing manual intervention and/or hopefully reduce the chance of the file getting corrupt and thus losing all the details associated with previous orders/positions.