Gamestudio Links
Zorro Links
Newest Posts
Data from CSV not parsed correctly
by EternallyCurious. 04/18/24 10:45
StartWeek not working as it should
by Zheka. 04/18/24 10:11
folder management functions
by VoroneTZ. 04/17/24 06:52
lookback setting performance issue
by 7th_zorro. 04/16/24 03:08
zorro 64bit command line support
by 7th_zorro. 04/15/24 09:36
Zorro FIX plugin - Experimental
by flink. 04/14/24 07:48
Zorro FIX plugin - Experimental
by flink. 04/14/24 07:46
AUM Magazine
Latest Screens
The Bible Game
A psychological thriller game
SHADOW (2014)
DEAD TASTE
Who's Online Now
1 registered members (1 invisible), 672 guests, and 0 spiders.
Key: Admin, Global Mod, Mod
Newest Members
EternallyCurious, howardR, 11honza11, ccorrea, sakolin
19047 Registered Users
Previous Thread
Next Thread
Print Thread
Rate Thread
Recover Orphan Trade #446528
10/20/14 06:12
10/20/14 06:12
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline OP
Serious User
DdlV  Offline OP
Serious User
D

Joined: Jun 2013
Posts: 1,609
Hi. Having been bit by this one again, I'd like to suggest that the popup window announcing the (possible) orphan trade be changed to a dialog requesting the Trade ID. If provided, when the user clicks OK Zorro can manage the trade. Otherwise, if no trade was actually entered the user can click Cancel.

Thanks.

Re: Recover Orphan Trade [Re: DdlV] #446533
10/20/14 13:58
10/20/14 13:58
Joined: Apr 2013
Posts: 57
3
3DCat Offline
Junior Member
3DCat  Offline
Junior Member
3

Joined: Apr 2013
Posts: 57
Also requesting an automatic email when a trade is orphaned.

Re: Recover Orphan Trade [Re: 3DCat] #446539
10/20/14 17:16
10/20/14 17:16
Joined: Jul 2000
Posts: 27,978
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,978
Frankfurt
That with Zorro managing an orphaned trade could be a bit difficult, as I can see several special cases where this won't work. An automated email makes sense of course.

Re: Recover Orphan Trade [Re: jcl] #446549
10/20/14 18:45
10/20/14 18:45
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline OP
Serious User
DdlV  Offline OP
Serious User
D

Joined: Jun 2013
Posts: 1,609
Certainly there could be problematic special cases, but the majority of the time it would simply be supplying the TradeID of the trade Zorro entered but didn't get back from the broker. Zorro should certainly check that the parameters of the trade entered match what it tried to do before accepting management of the trade, including that entry was within some time window of attempt, and anything that doesn't match is simply out of scope.

Thanks.

Re: Recover Orphan Trade [Re: DdlV] #446606
10/22/14 17:39
10/22/14 17:39
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline OP
Serious User
DdlV  Offline OP
Serious User
D

Joined: Jun 2013
Posts: 1,609
Or, other ideas:

- Share the layout of the .trd file, so the adventurous could add the trade
- Add a <scriptname>_unconfirmed.trd file, to capture the known info about the trade
- Perhaps the base case could be as simple as updating the empty ID in the latter and then appending to .trd?
- Or help with the list of other fields that get updated with data from the broker's confirmation?

Thanks.

Re: Recover Orphan Trade [Re: DdlV] #446607
10/22/14 17:43
10/22/14 17:43
Joined: Jul 2000
Posts: 27,978
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,978
Frankfurt
I can think of a method: Zorro writes the intended parameters of orphaned trades in a list in a text file, and takes over a trade when someone edits that file and inserts the TradeID. This could work if it wasn't too long ago.

Re: Recover Orphan Trade [Re: jcl] #446608
10/22/14 18:12
10/22/14 18:12
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline OP
Serious User
DdlV  Offline OP
Serious User
D

Joined: Jun 2013
Posts: 1,609
Thanks jcl. My use case would be as soon as I looked and saw the popup, so shouldn't be "too long ago". And possibly sooner with some of the other suggestions implemented - email notification, monitoring w/ notification...

Thanks.

Re: Recover Orphan Trade [Re: DdlV] #448474
02/06/15 01:23
02/06/15 01:23
Joined: Sep 2013
Posts: 64
Spain
yosoytrader Offline
Junior Member
yosoytrader  Offline
Junior Member

Joined: Sep 2013
Posts: 64
Spain
Hi guys, I've had a lot of orphaned trades since I started in January the demo accounts with FXCM ,
so today I decided to close them all: from 25 open trades in the account ..about 12 were orphaned trades, since the begining of January, just in 1 account, trading only Z12, and also had a similar number of orphaned trades in another account with Z1 in a separate PC.

For 1 hour the orphaned trade does not appear in FXCM Trading Station either, and in fact, if I try to open a trade manually for the same asset I get the same error #70, so it's not possible to close it until it appears in the Trading Station.

It would nice that FXCM would fix this issue, ..


in the meantime, why not let Zorro, when there's an orphaned trade, keep a list of them and attach automatically the Ticket when the trade is later confirmed by FXCM? Even if many strategies are running on the same PC I don't see the issue,

Otherwise, if finally the masters decide to implement a manual and simple but effective procedure it would be much appreciated. As I said today I closed like 12 trades in Z12 and this way is difficult to asses the real performance of the Z strategy,

happy trading


Happy trading laugh
Re: Recover Orphan Trade [Re: yosoytrader] #448480
02/06/15 09:14
02/06/15 09:14
Joined: Jul 2000
Posts: 27,978
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,978
Frankfurt
12 orphaned trades is not normal. I have normally about 2 orphaned trades per year. It could be a problem with the internet connection, for instance when it is frequently interrupted for a short time.


Moderated by  Petra 

Gamestudio download | chip programmers | Zorro platform | shop | Data Protection Policy

oP group Germany GmbH | Birkenstr. 25-27 | 63549 Ronneburg / Germany | info (at) opgroup.de

Powered by UBB.threads™ PHP Forum Software 7.7.1