never mind, its working, thanks..
Why does this happen ?
Betfair Down / Betfair site crash
I
Bought a registration yesterday. My card got declined (only because i had put wrong flaming expiry date in) After realising and correcting i got a slight flash of registration number
and logged in without actually putting in that number. Now V160 i cant log in to my account and the funds were taken successfully.
Is this a fault of the API between BF and BA but whats also strange is i never recieved a confirmation email which usually has the registration number on.
Confused unable to trade dont want no more days off
Alpha
Bought a registration yesterday. My card got declined (only because i had put wrong flaming expiry date in) After realising and correcting i got a slight flash of registration number
and logged in without actually putting in that number. Now V160 i cant log in to my account and the funds were taken successfully.
Is this a fault of the API between BF and BA but whats also strange is i never recieved a confirmation email which usually has the registration number on.
Confused unable to trade dont want no more days off


Alpha
We are seeing some odd issues with logging into Betfair at the moment. It only seems to be affecting a minor number of users. So we are working on trying to understand what's happening.
People seems to be able to log in using the interactive login.
People seems to be able to log in using the interactive login.
-
- Posts: 60
- Joined: Thu Oct 24, 2019 8:26 pm
yes me too, I used the interactive login for the first time last night after finally updating to version 1.6, using two versions older prior to that, Betfair account for yonks and Betangel user for about 3yrs.
I also did the classic restart of my PC, I generally keep it in sleep mode, this morning the login worked as normal (non interactive).
I also did the classic restart of my PC, I generally keep it in sleep mode, this morning the login worked as normal (non interactive).
-
- Posts: 568
- Joined: Tue Feb 14, 2017 7:27 pm
Ladders seem stick so far today - Perth just know was quite jerky in-play.
Overnight I received the following in Guardian (UK time):
24/08/2023 04:34:41: [G_Auto 1] : APING Exception: APING,market id passed is invalid . - 32099|ANGX-0002|BetAngelHelper.APINGErrorData
Anyone seen such errors before?
I had bets placed and matched at 1.01/1000 at the same second in a different market in what was supposed to be a pre-race market, with Guardian log showing the race turning in-play at 04:35:01, and all my bets stood so presumably something funky has happened here – still trying to figure out what happened.
24/08/2023 04:34:41: [G_Auto 1] : APING Exception: APING,market id passed is invalid . - 32099|ANGX-0002|BetAngelHelper.APINGErrorData
Anyone seen such errors before?
I had bets placed and matched at 1.01/1000 at the same second in a different market in what was supposed to be a pre-race market, with Guardian log showing the race turning in-play at 04:35:01, and all my bets stood so presumably something funky has happened here – still trying to figure out what happened.
-
- Posts: 1619
- Joined: Fri Nov 20, 2015 9:38 am
I had the Pakenham (AUS) 24th Aug - 04:30 R2 1400m Mdn go inplay at 04:33:19. It was suspended at 04:34:43 (due to race completing). If it was just AUS racing you were covering, next race Redcliffe went inplay at 4:42:30,,, Don't have anything around the 04:35:01 period...eightbo wrote: ↑Thu Aug 24, 2023 7:25 amOvernight I received the following in Guardian (UK time):
24/08/2023 04:34:41: [G_Auto 1] : APING Exception: APING,market id passed is invalid . - 32099|ANGX-0002|BetAngelHelper.APINGErrorData
Anyone seen such errors before?
I had bets placed and matched at 1.01/1000 at the same second in a different market in what was supposed to be a pre-race market, with Guardian log showing the race turning in-play at 04:35:01, and all my bets stood so presumably something funky has happened here – still trying to figure out what happened.
Thankssionascaig wrote: ↑Thu Aug 24, 2023 8:06 amI had the Pakenham (AUS) 24th Aug - 04:30 R2 1400m Mdn go inplay at 04:33:19. It was suspended at 04:34:43 (due to race completing). If it was just AUS racing you were covering, next race Redcliffe went inplay at 4:42:30,,, Don't have anything around the 04:35:01 period...eightbo wrote: ↑Thu Aug 24, 2023 7:25 amOvernight I received the following in Guardian (UK time):
24/08/2023 04:34:41: [G_Auto 1] : APING Exception: APING,market id passed is invalid . - 32099|ANGX-0002|BetAngelHelper.APINGErrorData
Anyone seen such errors before?
I had bets placed and matched at 1.01/1000 at the same second in a different market in what was supposed to be a pre-race market, with Guardian log showing the race turning in-play at 04:35:01, and all my bets stood so presumably something funky has happened here – still trying to figure out what happened.
The closest I have / next race (Warwick R3) turned in-play in my log at 04:35:23 and finishing at 04:36:25, which seems about right for 04:35 scheduled start time / 1100m race distance.
No issues with same automation file on rest of the AUS card tonight, just the one posted.