- ago
I've sporadically encountered the following error several times, maybe once or twice per day over the past week, where I get "CancelPending" in the Order Manager even though an Order actually completed successfully. I believe this has happened for both Coinbase and KuCoin, so is not broker-specific.

The bad part is that the Strategy seems to be in a busted state when this happens, so I have to force-kill the order to get it out of the Order Manager, and then manually press "Request Update from Broker" to get the Position to disappear from the Accounts window.

It seems like WL8 would be able to gracefully handle this situation on its own, if it wanted, by automatically requesting the update from the broker after the CancelPending failure. Maybe this is a situation that will be resolved by the upcoming change that allows using live position syncing rather than backtest positions.

Here's the full log file in case it's useful:
https://www.dropbox.com/s/0r985heleee3onf/error_cancel_pending_log.txt?dl=0

0
358
7 Replies

Reply

Bookmark

Sort
Cone8
 ( 24.57% )
- ago
#1
CancelPending is a canned status that's applied just before the order cancel is initiated. The error is the result of canceling the order with the broker. Especially because this was a Market order, the actual problem seems to be that something when wrong with the response for (or lack of) the sell order.

There wasn't a problem with the first round trip, but in both cases the Buy order was filled with a decimal amount that didn't appear in the exit orders. Glitch will have to look at it, but maybe this influenced [not] synching the position with the transaction. I know he had to go through great lengths to determine fill prices since they're not reported by KuCoin.
1
Glitch8
 ( 10.41% )
- ago
#2
Looking at the log it looks like unstable internet connection issues here.
0
- ago
#3
True, it does have that appearance. But I also run into this error when running strategies on AWS where unstable internet should not be an issue. I'll see if I can grab a screenshot and logs from one of those cases.
0
- ago
#4
Here is a CancelPending error that just occurred on an AWS machine. As usual when this happens, this order actually succeeded, and after pressing "Request Update from Broker" I see the information about the Position that was created.

Log file: https://www.dropbox.com/s/xcjtbtzvspphsam/error_cancel_pending_2.txt?dl=0

0
Cone8
 ( 24.57% )
- ago
#5
We removed the Coinbase provider from the Extensions. By the looks of the error, Coinbase has transitioned or is transitioning to their new "Advanced Trade API". Additionally, someone (from Coinbase? - it's not clear) served us a vague copyright infringement claim, so taken together, we're not supporting Coinbase for the time being.
0
- ago
#6
Oh man, that's really unfortunate news. I can't imagine there's anything legitimate about the infringement claim. Hopefully it's something that can be sorted out, because aside from this minor hiccup, the Coinbase extension was working exceedingly well for me.
0
Glitch8
 ( 10.41% )
- ago
#7
I have a feeling it’s just some flunky staff member who gets paid to find “infringers” online and report them. I doubt we’ll be able to penetrate Coinbase and reach anyone there who can really make a difference
but you never know 🤷🏼‍♂️
1

Reply

Bookmark

Sort