Yeah, that sounds like the API just randomly misbehaving. It is a Saturday afternoon after all!Trader Pat wrote: ↑Sat Jun 20, 2020 4:51 pmMy problem wasn't when I was greening so it might be something different.
Bet Angel V1.54.2 - Greening Fix from API Issues
-
- Posts: 144
- Joined: Sun May 10, 2020 12:55 pm
they were back bets for 1 tick offset, back fav, not taking bet, but if I backed another horse in ladder the trade would go in and cancel no problem. I supsect there may be an issue somewhere.... which at some point will disappear again?? it all seemed ok unitl they had that planned outage....
Woke up this morning seeing some issues with greening with Australian racing while using v1.54.2.
21/06/2020 : Cancelling bets 202850487588
21/06/2020 : Cancelling bets 202850487552
21/06/2020 : Placed closure bet with greening on X by Laying 83.79 at 8.8
21/06/2020 : Placed closure bet with greening on X by Laying 57.79 at 9.2
21/06/2020 : Cancelling bets 202850490494
21/06/2020 : Cancelling bets 202850493634
21/06/2020 : Placed closure bet with greening on X by Backing 62.97 at 9.2
21/06/2020 : Cancelling bets 202850497179
21/06/2020 : Cancelling bets 202850497177
21/06/2020 : Placed closure bet with greening on X by Backing 33.63 at 8.8
21/06/2020 : Cancelling bets 202850500366
21/06/2020 : Cancelling bets 202850503426
21/06/2020 : Cancelling bets 202850506624
21/06/2020 : Cancelling bets 202850509716
21/06/2020 : Cancelling bets 202850512683
21/06/2020 : Cancelling bets 202850515193
21/06/2020 : Cancelling bets 202850518137
21/06/2020 : Cancelling bets 202850520942
21/06/2020 : Cancelling bets 202850523525
21/06/2020 : An error occurred while cancelling bets: The order cannot be processed as the market is suspended.
21/06/2020 : An error occurred while Placing closure bet with greening on Y by Laying 1.27 at 30 [stage 1S]
This resulted in a 2 pound open position on Y. The Cancellations subsequent 07:55:05 are all greening attempts.
Another Example:
21/06/2020 : £ 2.00 Back bet placed on A at 7.6. £ 1.23 matched at 7.6 £ 0.77 unmatched when it initially reached the market. Ref: 202850002423 ( Fill or kill bet with 0.5 seconds delay. )
21/06/2020 : £ 0.77 unmatched bet (Ref:202850002423) was killed.
21/06/2020 : Placed closure bet with greening on C by Backing 8.39 at 5
21/06/2020 : Cancelling bets 202850084369
21/06/2020 : Cancelling bets 202850088827
21/06/2020 : Cancelling bets 202850093324
21/06/2020 : Cancelling bets 202850099845
21/06/2020 : Cancelling bets 202850105049
21/06/2020 : Cancelling bets 202850110894
21/06/2020 : Cancelling bets 202850115974
21/06/2020 : Cancelling bets 202850120227
21/06/2020 : Cancelling bets 202850124615
21/06/2020 : Cancelling bets 202850128238
21/06/2020 : Cancelling bets 202850132194
21/06/2020 : Cancelling bets 202850137281
21/06/2020 : Cancelling bets 202850141281
21/06/2020 : Cancelling bets 202850144673
This resulted in a 1.23 open position on A. 1 or 2 other examples.
EDIT: Another 2 pound back bet at odds 6.22 failed to green. Another 2 pound back bet at 8.2 failed to green. Note, these are attempts to green selections individually, not "Green All"
21/06/2020 : Cancelling bets 202850487588
21/06/2020 : Cancelling bets 202850487552
21/06/2020 : Placed closure bet with greening on X by Laying 83.79 at 8.8
21/06/2020 : Placed closure bet with greening on X by Laying 57.79 at 9.2
21/06/2020 : Cancelling bets 202850490494
21/06/2020 : Cancelling bets 202850493634
21/06/2020 : Placed closure bet with greening on X by Backing 62.97 at 9.2
21/06/2020 : Cancelling bets 202850497179
21/06/2020 : Cancelling bets 202850497177
21/06/2020 : Placed closure bet with greening on X by Backing 33.63 at 8.8
21/06/2020 : Cancelling bets 202850500366
21/06/2020 : Cancelling bets 202850503426
21/06/2020 : Cancelling bets 202850506624
21/06/2020 : Cancelling bets 202850509716
21/06/2020 : Cancelling bets 202850512683
21/06/2020 : Cancelling bets 202850515193
21/06/2020 : Cancelling bets 202850518137
21/06/2020 : Cancelling bets 202850520942
21/06/2020 : Cancelling bets 202850523525
21/06/2020 : An error occurred while cancelling bets: The order cannot be processed as the market is suspended.
21/06/2020 : An error occurred while Placing closure bet with greening on Y by Laying 1.27 at 30 [stage 1S]
This resulted in a 2 pound open position on Y. The Cancellations subsequent 07:55:05 are all greening attempts.
Another Example:
21/06/2020 : £ 2.00 Back bet placed on A at 7.6. £ 1.23 matched at 7.6 £ 0.77 unmatched when it initially reached the market. Ref: 202850002423 ( Fill or kill bet with 0.5 seconds delay. )
21/06/2020 : £ 0.77 unmatched bet (Ref:202850002423) was killed.
21/06/2020 : Placed closure bet with greening on C by Backing 8.39 at 5
21/06/2020 : Cancelling bets 202850084369
21/06/2020 : Cancelling bets 202850088827
21/06/2020 : Cancelling bets 202850093324
21/06/2020 : Cancelling bets 202850099845
21/06/2020 : Cancelling bets 202850105049
21/06/2020 : Cancelling bets 202850110894
21/06/2020 : Cancelling bets 202850115974
21/06/2020 : Cancelling bets 202850120227
21/06/2020 : Cancelling bets 202850124615
21/06/2020 : Cancelling bets 202850128238
21/06/2020 : Cancelling bets 202850132194
21/06/2020 : Cancelling bets 202850137281
21/06/2020 : Cancelling bets 202850141281
21/06/2020 : Cancelling bets 202850144673
This resulted in a 1.23 open position on A. 1 or 2 other examples.
EDIT: Another 2 pound back bet at odds 6.22 failed to green. Another 2 pound back bet at 8.2 failed to green. Note, these are attempts to green selections individually, not "Green All"
You’ll need to use the second patch build 1.54.2b mentioned earlier in this thread.
Betfair seemed to change the parameters of the restriction yesterday morning that caused additional faults. The ‘b’ build handles those too. The download link is the same, it just shows ‘b’ in the version number in Bet Angel itself.
Betfair seemed to change the parameters of the restriction yesterday morning that caused additional faults. The ‘b’ build handles those too. The download link is the same, it just shows ‘b’ in the version number in Bet Angel itself.
Oh, missed that. Thanks!Bet Angel wrote: ↑Sun Jun 21, 2020 9:08 amYou’ll need to use the second patch build 1.54.2b mentioned earlier in this thread.
Betfair seemed to change the parameters of the restriction yesterday morning that caused additional faults. The ‘b’ build handles those too. The download link is the same, it just shows ‘b’ in the version number in Bet Angel itself.
-
- Posts: 1074
- Joined: Fri Nov 20, 2015 9:38 am
On the b version and the one previously (just over the last two days), when a bet is taken the offset appears on the ladder as expected but then disappears and the reappears again - less than a second between them...
The bet is correct (only one offset actually makes it to bf) but looks very strange as there could be different amounts of money waiting to be matched on each appearance.
(also been running a fairly large spreadsheet in the background (not linked to BA), so maybe caused by system resource issues my end but just wondering if anyone else experiencing this issue?)
The bet is correct (only one offset actually makes it to bf) but looks very strange as there could be different amounts of money waiting to be matched on each appearance.
(also been running a fairly large spreadsheet in the background (not linked to BA), so maybe caused by system resource issues my end but just wondering if anyone else experiencing this issue?)
-
- Posts: 144
- Joined: Sun May 10, 2020 12:55 pm
I think I have seen something similar, also today, I may have seen, but not able to confirm yet that when applying an offset bet on the back side, the lay isn't hitting the market. Will have a further look and see what happens.
-
- Posts: 1074
- Joined: Fri Nov 20, 2015 9:38 am
Its intermittent, no issues with the 12:30 at wolvs...MAGTRADEUK wrote: ↑Sun Jun 21, 2020 12:20 pmI think I have seen something similar, also today, I may have seen, but not able to confirm yet that when applying an offset bet on the back side, the lay isn't hitting the market. Will have a further look and see what happens.
Using the b version and just had my first rejection at a lower price with a lower value.
This is log
21/06/2020 20:29:46: Unable to place lay bet on Galatasaray at 1.08. Initial bet - That is not a valid price for this market.
21/06/2020 20:29:46: Exception: Key cannot be null.
Parameter name: key
Was a pennies (14p) laying at fixed stake
This is log
21/06/2020 20:29:46: Unable to place lay bet on Galatasaray at 1.08. Initial bet - That is not a valid price for this market.
21/06/2020 20:29:46: Exception: Key cannot be null.
Parameter name: key
Was a pennies (14p) laying at fixed stake
You do not have the required permissions to view the files attached to this post.
We’re going to improve the error messaging this week, but the liability limits will remain the same.
Laying pennies on a very low priced selection will create a liability of <2p and the rounding is so significant on that compared to the stake, that it’s exactly the type of bet that betfair want to prevent.
For example someone laying £1.49 at 1.01 would cost them 1p whereas it should cost 1.49p based on the price, but they’ll still gain the £1.49 the one in a hundred times that 1.01 loses. Not surprised betfair want to stop that, and hundreds of tiny bets hitting the exchange from various accounts is bad for API stability which hurts us all.
Laying pennies on a very low priced selection will create a liability of <2p and the rounding is so significant on that compared to the stake, that it’s exactly the type of bet that betfair want to prevent.
For example someone laying £1.49 at 1.01 would cost them 1p whereas it should cost 1.49p based on the price, but they’ll still gain the £1.49 the one in a hundred times that 1.01 loses. Not surprised betfair want to stop that, and hundreds of tiny bets hitting the exchange from various accounts is bad for API stability which hurts us all.