Hi jcl. I now have a reverse-orphan trade that I need to know how to handle. Reverse-orphan means it's closed but Zorro still thinks it's active. Here is what happened, and the questions I have:

a) On Friday, Z12 opened this last trade before Weekend:
Code:
[GBP/USD:CY:L1732] Long 2@1.6312 Risk 15$  at 16:11
Weekend at 05.09. 20:00................


b) Today (Sunday), Z12 began to try to close the trade while trading was still closed (per Trading Station) and while Zorro was still in Weekend (at default 2). These messages began to repeat:
Code:
Broker: Error - Market is closed. Any trading functionality is not available.

Broker: Close order failed 58631732
BrokerSell GBP/USD: 20026 ms
[GBP/USD:CY:L1732] Can't close 2@1.6224 at 19:00
Broker: Error - Market is closed. Any trading functionality is not available.

Broker: Close order failed 58631732
BrokerSell GBP/USD: 20022 ms
[GBP/USD:CY:L1732] Can't close 2@1.6205 at 19:00
Broker: Close order incomplete 58631732
Broker: Error 072 - Timeout 58631732
BrokerSell GBP/USD: 40918 ms
[GBP/USD:CY:L1732] Can't close 2@1.6205 at 19:00


c) Question 1: Since FXCM Trading was still closed (per Trading Station), how valid/bogus were the prices Z12 was receiving and on which it based the close decision? Is Weekend=2 the correct value to use for FXCM?

d) Since all Trading was still closed, this trade could not be closed, but Z12 kept trying & logging messages like the above every minute or so. This seems to be normal functioning for Weekend=2 from what's in the manual, except that at each attempt Z12 went "Not responding" during most of this time - Question 2: Is Zorro being hung up by the API?

e) Immediately when Trading opened at 21:00, Trading Station reported the trade as closed. 2 problems:

f) Question 3: The close price recorded in Trading station is 1.61551. The price in Zorro's log at 20:00 is 1.6199. Why the difference?

g) Zorro did not recognize that the trade had been closed. The messages changed and the bogus trade # makes its 1st appearance:
Code:
Broker: Error - Cannot find a trade for order : 124059651@xxxxxxxx

Broker: Close order incomplete 58631732
Broker: Error 072 - Timeout 58631732
BrokerSell GBP/USD: 40939 ms
[GBP/USD:CY:L1732] Can't close 2@1.6173 at 21:00
Broker: Close order incomplete 58631732
Broker: Error 072 - Timeout 58631732
BrokerSell GBP/USD: 40913 ms
[GBP/USD:CY:L1732] Can't close 2@1.6173 at 21:00


h) At 23:00 Z12 went off Weekend and the logged messages became:
Code:
Weekend ends at 07.09. 23:00
[GBP/USD:CY:L1732] TMF stop after 0 bars
Broker: Error - Cannot find a trade for order : 124061545@xxxxxxxx

Broker: Close order failed 58631732
BrokerSell GBP/USD: 20023 ms
[GBP/USD:CY:L1732] Can't close 2@1.6221 at 22:58
Broker: Close order incomplete 58631732
Broker: Error 072 - Timeout 58631732
BrokerSell GBP/USD: 40966 ms
[GBP/USD:CY:L1732] Can't close 2@1.6221 at 22:58
Broker: Error - Cannot find a trade for order : 124061549@xxxxxxxx

Broker: Error - Cannot find a trade for order : 124061551@xxxxxxxx

Broker: Close order failed 58631732
BrokerSell GBP/USD: 20014 ms
[GBP/USD:CY:L1732] Can't close 2@1.6220 at 23:00


i) The last 4 messages have repeated continuously since then, and Z12 still thinks the trade is open. The bogus order number appears to be time-stamp related, as the 6th digit seems to increment every hour.

j) Now, whenever Z12 tries to close that trade it goes "Not responding" for about 20 seconds. The VPS is also running 2 other Zorro instances, and those 2 also go unresponsive (as judged by their clocks not incrementing) for the same 20 seconds. Question 4: Is this because they're all running through the same API? Is ticks processing for all also suspended & ticks dropped?! Is this a reason to not run multiple instances on the same machine/VPS?

k) And, of course, the final Question 5: How do I get Z12 to recognize that the trade is closed?!

Thanks.