Author |
Topic: Trailing Stop and Trailing Stop Limit order - version issue (3 messages, Page 1 of 1) |
||||
---|---|---|---|---|---|
Moderators: VPfau | |||||
MFrasson3344 Posts: 45 Joined: Nov 09, 2015 |
There is a bug in the "Versions" collection (GF API) of a Trailing Stop and Trailing Stop Limit order.
I'm using the new GF API, but i found the issue with old OEC api and with "Gain Trader Developer" application (lastest version) too. I used a Demo account + developer account (I hope the problem is not in the live accounts! please check). To reproduce the issue: Place a Trialing Stop order and wait for it to follow the market. The first automatic change to the order is performed correctly, but after this the "Versions" collection always contains the same data that correspond to the second version of the order. This is an example of the order versions collection: {Sell 1 ESM20 3194.00 Trailing Stop, Ref Price: 3197.5, Delta: 0} (Order creation version) {Sell 1 ESM20 3194.25 Trailing Stop, Ref Price: 3197.5, Delta: 0} (first auto modification) --> OK {Sell 1 ESM20 3194.25 Trailing Stop, Ref Price: 3197.5, Delta: 0} (second auto modification) --> NOT OK!! Same as the first modification {Sell 1 ESM20 3194.25 Trailing Stop, Ref Price: 3197.5, Delta: 0} NOT OK! Same as the first modification {Sell 1 ESM20 3194.25 Trailing Stop, Ref Price: 3197.5, Delta: 0} NOT OK! Same as the first modification {Sell 1 ESM20 3194.25 Trailing Stop, Ref Price: 3197.5, Delta: 0} NOT OK! Same as the first modification {Sell 1 ESM20 3194.25 Trailing Stop, Ref Price: 3197.5, Delta: 0} NOT OK! Same as the first modification We are near to release a new version of our application with new GF API and i would like to understand if this is an API issue or a server issue or both. Thank you for your collaboration. Mauro frasson Edited by MFrasson3344 on Jun 09, 2020 07:08 AM |
||||
SRuscak Posts: 50 Joined: Aug 24, 2017 |
Yes, you are correct, thank you. It's a server side issue. We're working on it and will get it fixed soon.
|
||||
CMicciche902 Posts: 367 Joined: |
Mauro,
We're not seeing this issue in production. Chris M
|
||||