I've noticed my "cancel bets and fully hedge market" automation rule (takes best available price) ends up firing super late if my original exit (offered exit for better price) gets partially tagged when the cancel is scheduled to fire.
Sometimes I've seen my offered exit get partially tagged like 4 times and it feels like each time I get matched it interrupts the cancel order or something. Is this all in my head or is it a known issue with the API? Any info greatly appreciated.
MuchO thankO
Are BET CANCELs interrupted if your offer gets partially filled at same time?
Not sure on the BA internals or what tagging means but when you place a cancel and it gets matched or semi matched during the cancel request the response will just include an updated sizeMatched / sizeCancelled. There is no extra delay due to this, however the matcher can and regularly does send a cryptic error instead if your order happens to match at a similar time to your cancel.
But tbh this sounds like a BA issue / delay.
But tbh this sounds like a BA issue / delay.
+ 1
Has happened to me several times. Now i dont bother with the offset in parameters tab but have an additional trigger to place the offset if opening bet is matched or part matched and then another trigger to cancel any unmatched part bets.
Hmm alright guys thanks. Linus if something is tagged it got hit/touched in some way, usually partially.
Not offsetting post-cancel so even if it fails my code should just fire another cancel order 20-100ms later on the next cycle depending on how many active mkts are running so don't think it will make as big of an impact as I was concerned with initially
Not offsetting post-cancel so even if it fails my code should just fire another cancel order 20-100ms later on the next cycle depending on how many active mkts are running so don't think it will make as big of an impact as I was concerned with initially