New beta version of Bet Angel v1.61.0 - Now on general release

[weemac]

Don't know if it's a BA bug or not, but the exported SV's for 2 horses in the Yarmouth 14:35 are showing as having hundreds of days since they last ran, but they actually ran recently, in the same country and the same code.

Belgoprince 15:40 today: SV returns 610 days compared to 40 days in reality.

Did you check what was showing in the yellow pop up box when you hover your cursor over the jockey silks on the One-Click screen?
and what Betfair had on there website when hovering over a selections name?

No, I don't use the one click screen, but I'll check next time I see one that's different.

[weemac]

Belgoprince 15:40 today: SV returns 610 days compared to 40 days in reality.

Did you check what was showing in the yellow pop up box when you hover your cursor over the jockey silks on the One-Click screen?
and what Betfair had on there website when hovering over a selections name?

No, I don't use the one click screen, but I'll check next time I see one that's different.

Major Gatsby Chep 5:10. Shows 241 on the pop-up; 33 on the website. 33 is correct.

[Dallas]

Did you check what was showing in the yellow pop up box when you hover your cursor over the jockey silks on the One-Click screen?
and what Betfair had on there website when hovering over a selections name?

No, I don't use the one click screen, but I'll check next time I see one that's different.

Major Gatsby Chep 5:10. Shows 241 on the pop-up; 33 on the website. 33 is correct.

Yep, I can see that, so Betfair have it wrong on their API and the SV will pick up the same as what appears in the yellow pop up box

[weemac]

No, I don't use the one click screen, but I'll check next time I see one that's different.

Major Gatsby Chep 5:10. Shows 241 on the pop-up; 33 on the website. 33 is correct.

Yep, I can see that, so Betfair have it wrong on their API and the SV will pick up the same as what appears in the yellow pop up box

Do BA have an avenue of influence to ask BF to sort it out?

[Dallas]

Major Gatsby Chep 5:10. Shows 241 on the pop-up; 33 on the website. 33 is correct.

Yep, I can see that, so Betfair have it wrong on their API and the SV will pick up the same as what appears in the yellow pop up box

Do BA have an avenue of influence to ask BF to sort it out?

We could flag it to them, but its probably been like that for some time, when there was just the pop up window no one probably took much notice or referred to the website to see the runner info

[ShaunWhite]

Major Gatsby Chep 5:10. Shows 241 on the pop-up; 33 on the website. 33 is correct.

Yep, I can see that, so Betfair have it wrong on their API and the SV will pick up the same as what appears in the yellow pop up box

Do BA have an avenue of influence to ask BF to sort it out?

I can't see how that's happened, the api is what drives the website.

[Bet Angel]

Major Gatsby Chep 5:10. Shows 241 on the pop-up; 33 on the website. 33 is correct.

I just checked that against the data we were sent on the betfair API and yes the API had the DAYS_SINCE_LAST_RUN set to 241.
So not a bug in Bet Angel, but we'll mention it to betfair in case they are not aware.

[Bet Angel]

I can't see how that's happened, the api is what drives the website.

The API and the web site must be disconnected as both 'Bringbackmemories' and 'Cedar Rapids' at Ripon today (14:15) are showing different Days Since Last Run values as I type this. Anyway, we've flagged it to betfair now.

[weemac]

Thanks for flagging it to BF. I'm sure they wouldn't want to be known for sending out inaccurate information!

[ilovepizza82]

And again
Never had problem with this before with previous versions. It happens on a regular basis.
Im uninstalling this nonsense untill its fixed. Cant risk my money. Sorry.

31/08/2023 12:01:23: £ 50.00 Back bet placed on Celtic Warrior at 18. £ 8.43 matched at 18.3309608540925 £ 41.57 unmatched when it initially reached the market. Ref: 319063567798
31/08/2023 12:01:31: Modify bet 319063567798 from 41.57 @ 18 to 41.57 @ 15 New Ref: 319063581113
31/08/2023 12:01:34: Modify bet 319063581113 from 24.04 @ 15 to 24.04 @ 14.5 New Ref: 319063587758
31/08/2023 12:01:35: Modify bet 319063587758 from 19.28 @ 14.5 to 19.28 @ 14 New Ref: 319063589407
31/08/2023 12:01:37: Modify bet 319063589407 from 19.28 @ 14 to 19.28 @ 13.5 New Ref: 319063592368
31/08/2023 12:01:38: Modify bet 319063592368 from 13.82 @ 13.5 to 13.82 @ 13 New Ref: 319063594023
31/08/2023 12:08:44: £ 5.00 Lay bet placed on Celtic Warrior at 14. Entirely unmatched when it initially reached the market. Ref: 319064228226
31/08/2023 12:08:48: Modify bet 319064228226 from 5 @ 14 to 5 @ 14 [Keep at in-play]
31/08/2023 12:46:02: Guardian has detected that the market is suspended
31/08/2023 12:46:03: Guardian has detected that the market is now unsuspended
31/08/2023 14:24:42: £ 5.00 Lay bet placed on Celtic Warrior at 12.5. Fully matched at 12.5. Ref: 319075287966

[Bet Angel]

At the moment you're the only customer that has reported these issues and the beta has used by loads of people totalling thousands of hours, so there must be something different about your settings, usage, PC, internet etc (can't rule anything out at this stage). It won't be long until this beta goes into full general release, so we'd really like to fully understand what's going on before that.

Do you toggle between Streaming or non-Streaming, or power-save the PC to sleep for a while since placing the first bet, or modify restricted refresh settings? There must be something pretty unique about what you're doing. Although you've seen this happen on a regular basis, we've only had a few reports on this thread, so haven't had enough detail to form a pattern.

Your Guardian image is showing 2 matched bets, but which bet refs in that log were the matched ones on the Matched Bets page? Guardian also isn't showing the 'Last Update' column so we can't see when it was last refreshed. It's not possible to tie everything together with just a consolidated view of bets on betfair (i.e. no bet references) and no Matched Bets page from Guardian. Ideally when you see it, you'd capture every bet reference, grab an image of the ladder showing the relevant selection and perhaps start a second instance of Bet Angel to check that matches the betfair web site.

The more you can capture, and the more you can experiment with your Bet Angel usage, the better the chance we've got of finding the cause and preventing it. If you don't want to put everything on this public forum, you can raise a ticket with our support inbox.

[sniffer66]

Just wanted to check something on timing loading a coupon via the BA API. If I load a coupon of say, 1000 markets. In guardian it will show x markets initialising for a couple of minutes,. At what point will a query of market type i.e football, return a true result ? Immediately, or do I need to wait for the 2 minutes for all markets to be initialised for that return to be exact? Obviously I don't know how long the markets will take to initialise so if it's the second how can I tell when they are all in Guardian?

[Bet Angel]

You should wait for Guardian to cycle through all the markets so that everything is initialised.
You can estimate how long that’ll take by multiplying the number of markets by the Guardian refresh interval, but could just call getMarkets from time to time to see how it’s getting on. You’ll get all the market ids immediately and as they initialise the markets will contain other details such as Name and Event ID.

[eightbo]

Bug (v1.60.0)
Probably also in v1.61.0 unless it was already reported & dev(s) fixed it

Storing values with comma(s) breaks the 'Export All Stored Values' Rule type CSV exporting
i.e. one SV pair pre-export gets split up into multiple SV pairs post-export.

Example:

Code: Select all

BA SV  (name): StoredValue,With,Commas
BA SV (value): 8

...gets exported as:

Code: Select all

.csv SV 1  (name): StoredValue
.csv SV 1 (value): With
.csv SV 2  (name): Commas
.csv SV 2 (value): 8

Didn't test but presumably this breaks the "Count of name/value pairs in this Section before next Section column" calculation
(however this can be ignored presuming a direct fix is possible)

Possible solutions:
      (direct fix):  Manipulate "," in SV string before exporting
  (workaround):  Remind users with a small, hoverable info button that commas aren't csv-friendly.

[eightbo]

We are pleased to announce that a new beta version of Bet Angel Professional is available v1.61.0 beta1

Automation - Editor & Conditions

• When using 'Export All Stored Values' there is now an option to 'Limit export to specific Stored Value Names'
  • i.e. you can enter a list of SV Names that you are interested in, and only they will be exported.

Great initial steps.

Please could you expand this to make use of the functionality already available in the Text Comparison condition.

Right now we are basically limited to 'exactly matches one of the following'.
Expanding to the list below will allow BA users to define their own variable naming structures on the fly without ever having to actively manage the exported SV lists.

It'd be 100% frictionless to set 'starts with one of the following' and prefix SV's as needed, meaning zero SV-export data entry while building.
Across all files that's a huge time save for the community.  Plus presumably, you already have the sub-routines ready to go so — low effort, high reward.

i.e.

◘.png