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.
Bet Angel V1.54.2 - Greening Fix from API Issues
-
- Posts: 1088
- 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: 1088
- 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.
- speedyhamster
- Posts: 119
- Joined: Fri Sep 22, 2017 9:58 am
What a farce all Betfair needed to do is change everybody's account to 4 decimal places(only show 2 pl;aces on account) so a 1.49p liability would show as £0.0149 internally so in the long term you don't gain any rounding. So lots of small bets hitting the market would be a waste of time?
That is a good idea, if it doesn't involve rewriting a lot of code. But I'm glad Betfair are trying to do something to stop these penny-shaving scumbags.speedyhamster wrote: ↑Mon Jun 22, 2020 2:06 amWhat a farce all Betfair needed to do is change everybody's account to 4 decimal places(only show 2 pl;aces on account) so a 1.49p liability would show as £0.0149 internally so in the long term you don't gain any rounding. So lots of small bets hitting the market would be a waste of time?
I'd much rather they gave you a limit (like turnover charge) of how many sub 10 pence bets you place on one market and charge you for exceeding the limit. Then you simply green-up on all selections before the off, if desired.
A lot depends on the actual stake and price being used when hedging, but any lay bet with a liability of 2p or more seems to be ok, so you'll be able to hedge profits to be very close to each other.
Thanks. We're used to seeing minor discrepancies with small profits due to rounding and if that dicrepancy is a little bigger in future then so be it - but I'm more concerned that we'll find ourselves unable to hedge at all in some circumstances. Many automation files for instance use even stakes to back and lay many times and possibly multiple runners and then hedge just before the off - it would be worrying if only some things got hedged.