Request for Assistance: Bet Angel/Betfair Technical Issue

Advanced automation available in Guardian - Chat with others and share files here.
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

jamesedwards wrote:
Tue May 21, 2024 1:37 pm
Betfair was down for planned maintenance between 6am and 8am (british summer time) this morning.

It's only a guess, but perhaps the Betfair API was not returning correct info data to Bet Angel at the exact time that it was placing bets, and if your rules rely on volume/value of bets placed then it's possible Bet Angel kept firing. If Betfair API doesn't tell BA that bets are placed then BA will, of course, act as if they don't exist.

A similar thing happened to me once when someone switched off my internet briefly in the middle of a trade. It's best to add conditions to rules that protect from these rare events. It's also a good idea to switch off automation during periods of planned Betfair maintenance. Also if you want to limit your exposure you should reduce the exposure limit with Betfair themselves in addition to anything you have set in BA.
That's a good idea. I thought I had that solved already. Can you suggest specific conditions to use?
User avatar
jamesedwards
Posts: 4369
Joined: Wed Nov 21, 2018 6:16 pm

lotora wrote:
Tue May 21, 2024 1:51 pm
jamesedwards wrote:
Tue May 21, 2024 1:42 pm
lotora wrote:
Tue May 21, 2024 1:33 pm


1. Do you have any idea why my Bet Angel log is completely empty?
2. Is there any method to extract my trades from this single greyhound race, given that I have not used the "Export reports on market closure" feature?
Have you checked the relevant file in this folder?

C:\Users\YOURPCUSERNAME\AppData\Roaming\Bet Angel\Bet Angel Professional\MarketReports
I'm using Bet Angel VPS. Couldn't find it
The AppData folder might be hidden.
Last edited by jamesedwards on Tue May 21, 2024 1:57 pm, edited 1 time in total.
User avatar
jamesedwards
Posts: 4369
Joined: Wed Nov 21, 2018 6:16 pm

lotora wrote:
Tue May 21, 2024 1:53 pm
jamesedwards wrote:
Tue May 21, 2024 1:37 pm
Betfair was down for planned maintenance between 6am and 8am (british summer time) this morning.

It's only a guess, but perhaps the Betfair API was not returning correct info data to Bet Angel at the exact time that it was placing bets, and if your rules rely on volume/value of bets placed then it's possible Bet Angel kept firing. If Betfair API doesn't tell BA that bets are placed then BA will, of course, act as if they don't exist.

A similar thing happened to me once when someone switched off my internet briefly in the middle of a trade. It's best to add conditions to rules that protect from these rare events. It's also a good idea to switch off automation during periods of planned Betfair maintenance. Also if you want to limit your exposure you should reduce the exposure limit with Betfair themselves in addition to anything you have set in BA.
That's a good idea. I thought I had that solved already. Can you suggest specific conditions to use?
Difficult without knowing what triggers your trades and what conditions you use. Can you post your rulefile here?
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

Yes!, after I have contacted BDP
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

Before contacting BDP, what to improve?

Subject: Urgent: Incorrect Exposure and Bet Settlement on Greyhound Race

Dear Betfair Developer Support,

I am writing to report a serious issue regarding my account's recent activity. I discovered a $323.30 loss on a single greyhound race, which exceeds the maximum exposure limit I have set for my software, Bet Angel. This is highly unusual as my betting is fully automated, and I have never traded such high stakes on this race. I have placed many thousands of trades without this ever happening before.

When I contacted Betfair chat, they sent me a file showing the bets placed on this specific greyhound race, but these bets differ from my Betfair 'Betting Profit and Loss' oversight, indicating a possible technical error.

Could you please investigate this issue urgently and assist in rectifying the erroneous transaction? Additionally, could you provide information on how these bets were placed?

There appears to be a discrepancy that needs immediate attention to ensure the accuracy and integrity of my account.

Thank you for your prompt assistance.

Best regards,
[Your Name]
[Your Betfair Username/Account Number]
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

jamesedwards wrote:
Tue May 21, 2024 1:56 pm
lotora wrote:
Tue May 21, 2024 1:53 pm
jamesedwards wrote:
Tue May 21, 2024 1:37 pm
Betfair was down for planned maintenance between 6am and 8am (british summer time) this morning.

It's only a guess, but perhaps the Betfair API was not returning correct info data to Bet Angel at the exact time that it was placing bets, and if your rules rely on volume/value of bets placed then it's possible Bet Angel kept firing. If Betfair API doesn't tell BA that bets are placed then BA will, of course, act as if they don't exist.

A similar thing happened to me once when someone switched off my internet briefly in the middle of a trade. It's best to add conditions to rules that protect from these rare events. It's also a good idea to switch off automation during periods of planned Betfair maintenance. Also if you want to limit your exposure you should reduce the exposure limit with Betfair themselves in addition to anything you have set in BA.
That's a good idea. I thought I had that solved already. Can you suggest specific conditions to use?
Difficult without knowing what triggers your trades and what conditions you use. Can you post your rulefile here?
Maybe I could post part of the file, but I believe this might be enough for now. Two of the conditions are:

Selections: Number of matched bets = 0
Number of unmatched bets = 0
As I mentioned, I have never had any issues with this bot and use it for hundreds of greyhounds bets every day. What I need is the option to stop firing bets when there are technical issues.
User avatar
Dabbla
Posts: 826
Joined: Wed Apr 15, 2009 1:50 pm

I also had a similar incident after maintenance. I forget exactly what happened but my automation kicked back in and placed lots of bets @1000 leaving my balance in the RED. Thankfully they could be cancelled and no harm was done.

I would have thought the BA exposure use the Betfair exposure as reference. If Betfair fails so does BA.

£111.11 is a £10 win @ odds of 1.09.
I suspect that the automation kicked in after the maintenance and placed bets at 1.09. Other people placed bets at the same time meaning you were matched at higher odds.
Maybe because of the amount of bets suddenly being placed on the exchange. The exposure limit was not sent correctly therefore bypassing the exposure limit.
User avatar
jamesedwards
Posts: 4369
Joined: Wed Nov 21, 2018 6:16 pm

lotora wrote:
Tue May 21, 2024 2:52 pm
jamesedwards wrote:
Tue May 21, 2024 1:56 pm
lotora wrote:
Tue May 21, 2024 1:53 pm


That's a good idea. I thought I had that solved already. Can you suggest specific conditions to use?
Difficult without knowing what triggers your trades and what conditions you use. Can you post your rulefile here?
Maybe I could post part of the file, but I believe this might be enough for now. Two of the conditions are:

Selections: Number of matched bets = 0
Number of unmatched bets = 0
As I mentioned, I have never had any issues with this bot and use it for hundreds of greyhounds bets every day. What I need is the option to stop firing bets when there are technical issues.
Difficult without seeing the full rulesfile. But if the only thing stopping bets from potentially infinitely triggering is a zero matched/unmatched bets condition then you do leave yourself at the mercy of an API data flow breakdown. For example, if Betfair API reports zero bets even if bets have been placed, then BA could keep triggering for as long as other conditions are met.

I would also set a stored value to your trigger, then you can add a condition that this SV is 'not set' to the same trigger, therefore preventing it from triggering more than once. This way BA no longer relies solely on Betfair to tell it that there is already a bet placed, it will be also checking it's own stored value condition.
User avatar
napshnap
Posts: 1234
Joined: Thu Jan 12, 2017 6:21 am

lotora wrote:
Tue May 21, 2024 2:52 pm
jamesedwards wrote:
Tue May 21, 2024 1:56 pm
lotora wrote:
Tue May 21, 2024 1:53 pm


That's a good idea. I thought I had that solved already. Can you suggest specific conditions to use?
Difficult without knowing what triggers your trades and what conditions you use. Can you post your rulefile here?
Maybe I could post part of the file, but I believe this might be enough for now. Two of the conditions are:

Selections: Number of matched bets = 0
Number of unmatched bets = 0
As I mentioned, I have never had any issues with this bot and use it for hundreds of greyhounds bets every day. What I need is the option to stop firing bets when there are technical issues.
thats a good thing, but it wont save you in this particular case, cause there were no errors returned in api responses - I checked it. Responses were empty (in normal condition they shouldn't if you have matched bets) - thats the problem. And Im afriad its unavoidable problem if your logic depends on specific conditions.
Last edited by napshnap on Tue May 21, 2024 3:37 pm, edited 4 times in total.
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

jamesedwards wrote:
Tue May 21, 2024 3:05 pm
lotora wrote:
Tue May 21, 2024 2:52 pm
jamesedwards wrote:
Tue May 21, 2024 1:56 pm


Difficult without knowing what triggers your trades and what conditions you use. Can you post your rulefile here?
Maybe I could post part of the file, but I believe this might be enough for now. Two of the conditions are:

Selections: Number of matched bets = 0
Number of unmatched bets = 0
As I mentioned, I have never had any issues with this bot and use it for hundreds of greyhounds bets every day. What I need is the option to stop firing bets when there are technical issues.
Difficult without seeing the full rulesfile. But if the only thing stopping bets from potentially infinitely triggering is a zero matched/unmatched bets condition then you do leave yourself at the mercy of an API data flow breakdown. For example, if Betfair API reports zero bets even if bets have been placed, then BA could keep triggering for as long as other conditions are met.

I would also set a stored value to your trigger, then you can add a condition that this SV is 'not set' to the same trigger, therefore preventing it from triggering more than once. This way BA no longer relies solely on Betfair to tell it that there is already a bet placed, it will be also checking it's own stored value condition.
Thank you! Please check the attached file. I've made some "meaningless" changes to protect my secrets :-)
You do not have the required permissions to view the files attached to this post.
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

Dabbla wrote:
Tue May 21, 2024 2:53 pm
I also had a similar incident after maintenance. I forget exactly what happened but my automation kicked back in and placed lots of bets @1000 leaving my balance in the RED. Thankfully they could be cancelled and no harm was done.

I would have thought the BA exposure use the Betfair exposure as reference. If Betfair fails so does BA.

£111.11 is a £10 win @ odds of 1.09.
I suspect that the automation kicked in after the maintenance and placed bets at 1.09. Other people placed bets at the same time meaning you were matched at higher odds.
Maybe because of the amount of bets suddenly being placed on the exchange. The exposure limit was not sent correctly therefore bypassing the exposure limit.
What I find alarming is that the bot placed back bets at odds far below the limits set in the conditions.
User avatar
jamesedwards
Posts: 4369
Joined: Wed Nov 21, 2018 6:16 pm

lotora wrote:
Tue May 21, 2024 3:29 pm
jamesedwards wrote:
Tue May 21, 2024 3:05 pm
lotora wrote:
Tue May 21, 2024 2:52 pm


Maybe I could post part of the file, but I believe this might be enough for now. Two of the conditions are:

Selections: Number of matched bets = 0
Number of unmatched bets = 0
As I mentioned, I have never had any issues with this bot and use it for hundreds of greyhounds bets every day. What I need is the option to stop firing bets when there are technical issues.
Difficult without seeing the full rulesfile. But if the only thing stopping bets from potentially infinitely triggering is a zero matched/unmatched bets condition then you do leave yourself at the mercy of an API data flow breakdown. For example, if Betfair API reports zero bets even if bets have been placed, then BA could keep triggering for as long as other conditions are met.

I would also set a stored value to your trigger, then you can add a condition that this SV is 'not set' to the same trigger, therefore preventing it from triggering more than once. This way BA no longer relies solely on Betfair to tell it that there is already a bet placed, it will be also checking it's own stored value condition.
Thank you! Please check the attached file. I've made some "meaningless" changes to protect my secrets :-)
Sorry but I can't view this because I havent yet upgraded to the latest beta version.
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

jamesedwards wrote:
Tue May 21, 2024 3:44 pm
lotora wrote:
Tue May 21, 2024 3:29 pm
jamesedwards wrote:
Tue May 21, 2024 3:05 pm


Difficult without seeing the full rulesfile. But if the only thing stopping bets from potentially infinitely triggering is a zero matched/unmatched bets condition then you do leave yourself at the mercy of an API data flow breakdown. For example, if Betfair API reports zero bets even if bets have been placed, then BA could keep triggering for as long as other conditions are met.

I would also set a stored value to your trigger, then you can add a condition that this SV is 'not set' to the same trigger, therefore preventing it from triggering more than once. This way BA no longer relies solely on Betfair to tell it that there is already a bet placed, it will be also checking it's own stored value condition.
Thank you! Please check the attached file. I've made some "meaningless" changes to protect my secrets :-)
Sorry but I can't view this because I havent yet upgraded to the latest beta version.
Okay! Will you please do it later?
User avatar
ForFolksSake
Posts: 945
Joined: Sat May 11, 2024 2:51 pm

lotora wrote:
Tue May 21, 2024 11:53 am
Hey, Bet Angel Support,

I am writing to seek your assistance regarding a technical issue I have encountered with Betfair. Recently, I was informed by Betfair via chat that I had lost $340 on a single horse race. This loss is perplexing and concerning as it exceeds my maximum exposure limit, which is only a fraction of that amount.

Additionally, my Betfair profit and loss statement has not been updated for the past two hours, and my Bet Angel log is completely blank. Furthermore, I have no information about which horse race this pertains to since it is not recorded in my log. This indicates a possible technical glitch. I firmly believe this issue is not related to my trading activities but rather a system error.

It is also important to note that my betting is 100% automated, making it theoretically impossible for me to lose such an amount. Moreover, I have never before experienced an empty log, which suggests that this issue might be related to the latest update of the Bet Angel software. Additionally, I do not use the "Export reports on market closure" feature, so I am unsure how I can find any information about my trading on this horse race.

I am currently awaiting further information from Betfair regarding the trades in question for this particular horse race. In the meantime, I would greatly appreciate your help in resolving this matter and assisting me in getting the money refunded.

Now my 'Betting Profit & Loss' has finally been settled, and I discovered that it all stemmed from a single greyhound race. Please check the two files attached file for details. I have never traded this race with such high stakes. So how do I get back the money? The Betfair representative had never heard about Bet Angel.

In the bot attached, 've made some "meaningless" changes to protect my secrets :-)

Latest edit: What I find alarming is that the bot placed back bets at odds far below the limits set in the conditions.



Thank you for your attention and support.
What I find alarming .... :shock:
If you find it alarming what are BF thinking.
It's not the $340 loss I would be worried about
Best of luck 🍀
Last edited by ForFolksSake on Tue May 21, 2024 6:29 pm, edited 2 times in total.
User avatar
jamesedwards
Posts: 4369
Joined: Wed Nov 21, 2018 6:16 pm

lotora wrote:
Tue May 21, 2024 3:48 pm
jamesedwards wrote:
Tue May 21, 2024 3:44 pm
lotora wrote:
Tue May 21, 2024 3:29 pm


Thank you! Please check the attached file. I've made some "meaningless" changes to protect my secrets :-)
Sorry but I can't view this because I havent yet upgraded to the latest beta version.
Okay! Will you please do it later?
Can you find this folder?

C:\Users\User\AppData\Roaming\Bet Angel\Bet Angel Professional\MarketReports

You should be able to find the Bet Angel log for that race in it.
Post Reply

Return to “Bet Angel - Automation”