The Order Manager shows no error, but my Market Sell displays status "Canceled" and I'm not sure why. Is there any way I can find out more about the reason for the cancelation? If WL8 knows that the order was canceled, shouldn't it retry the sell order later, before entering into the next new position (AXS/USD)?
Log File: https://www.dropbox.com/s/hfx13bylk61soi1/error_sell_canceled.txt?dl=0
Log File: https://www.dropbox.com/s/hfx13bylk61soi1/error_sell_canceled.txt?dl=0
Rename
I don't think the question should be why the order was canceled - that happened because the strategy executed for the next bar and the order was still active, so it's canceled. Orders are canceled when the strategy's logic doesn't signal the same order on the next bar.
The question is, "why didn't Coinbase execute the order. Based on the log, the strategy runs only take around 2 seconds, so presumably Coinbase has more than 50 seconds to execute a market order. It seems like the log starts after that order.
The question is, "why didn't Coinbase execute the order. Based on the log, the strategy runs only take around 2 seconds, so presumably Coinbase has more than 50 seconds to execute a market order. It seems like the log starts after that order.
Let's say Coinbase was having some sort of "service disruption" or something during that bar and didn't respond to the market sell in time (or at all). Is there any way to handle this situation with the current WL8 mechanisms, so that it retries to sell later, or at least recognizes that I still hold the position so it doesn't move on to entering a new position?
Is this situation something that would be handled gracefully by the upcoming live position sync in build 28?
Is this situation something that would be handled gracefully by the upcoming live position sync in build 28?
QUOTE:In this case, the current orphan logic would have worked too, but yes, the Live Position logic is tailored made to keep a strategy in sync with positions in the broker account.
Is this situation something that would be handled gracefully by the upcoming live position sync in build 28?
Your Response
Post
Edit Post
Login is required