Betfair Down / Betfair site crash

[Jamstee]

I've had about a dozen of these error messages today on various (but not all) goal markets throughout the day

14/04/2017 20:56:26: [G_Auto] : WARNING: Matched Bet information was not refreshed during the fill or kill processing which may lead to calculation problems. Check refresh rates to ensure frequent updates. (Ref: 90168971087)

14/04/2017 21:09:46: [G_Auto] : WARNING: Matched Bet information was not refreshed during the fill or kill processing which may lead to calculation problems. Check refresh rates to ensure frequent updates. (Ref: 90170072835)

I'm still fairly new to things here and although I've set up various automated trades so far, it's normally user error (wrong market choice, mis-reading play, sentimentality, etc) which has been costing me, so I'd created another rules file today to try and take some emotion out of the situation and thought this particular error was down to me till I just googled it and seen all these.

Thankfully I'd kept it limited to using small, fixed liabilities so I'm only looking at a loss of around £9 on the day - it had worked quite happily on the first 6 markets and was therefore happy to let it keep running and was looking forward to some nice profit at the end of the day, but on 12 occasions I've found so far (including 3 of them on one market), my subsequent back bet hasn't been placed, so any subsequent goal left me with a loss.

Can you suggest anything else to include in my rules file to ensure this doesn't happen again in the future (other than keep running the green up which I'd already included at more regular intervals)?

14/04/2017 21:05:04: Greened up Over 1.5 Goals by Backing 30.39 at 1.44?

Any assistance would be greatly appreciated

PS. I can't let my first post go by without passing on my thanks to all of you who have taken so much time and trouble to make this such a helpful and informative forum, and for all the ideas, templates, spreadsheets and suggestions which I've barely scratched the surface of.

Hopefully I too will have some ideas to add / files to share in the years to come if I'm even remotely as consistent as some of the members here!

[Dallas]

14/04/2017 20:56:26: [G_Auto] : WARNING: Matched Bet information was not refreshed during the fill or kill processing which may lead to calculation problems. Check refresh rates to ensure frequent updates. (Ref: 90168971087)

14/04/2017 21:09:46: [G_Auto] : WARNING: Matched Bet information was not refreshed during the fill or kill processing which may lead to calculation problems. Check refresh rates to ensure frequent updates. (Ref: 90170072835)

The most likely cause of this is you had too many markets in guardian and your refresh rate was set to slow to cycle through and refresh them all quick enough for your fill/kill to work correctly
This thread fully explains how guardian refreshes markets, have a read of that and think back to how you were set up and the refresh rates you were using etc and it should clear it all up for you
http://www.betangel.com/forum/viewtopic ... 37&t=11491


PS; welcome to the forum

[Jamstee]

Thanks for the prompt reply Dallas - yes, that makes perfect sense (I did have a lot of markets open trying to make sure I didn't miss any opportunities - typical newbie error I'm sure )

You're right - I was set at 500ms but only seem to be able to come as low as a 200ms refresh rate (not 20ms as you mention) and I am using v1.46.1.

I made some tweaks to my rules before I took my lad to the park during the Spurs game and left them running with 6 markets open (all goals markets) and came back to find no trades have gone through and the following showing in the log:-

15/04/2017 14:18:05: Exception caught while cancelling bet - Exception of type 'BetAngelHelper.APINGException' was thrown.
15/04/2017 14:18:05: WARNING: The Betfair API was unable to process the bet cancellation request. Second attempt activated. (Ref: 90216684606)
15/04/2017 14:18:05: Exception caught while cancelling bet - Exception of type 'BetAngelHelper.APINGException' was thrown.
15/04/2017 14:18:05: WARNING: The Betfair API was unable to process the bet cancellation on the second request. It could cause calculation problems with this fill or kill bet and may leave the bet active in the market. (Ref: 90216684606)
15/04/2017 14:18:05: Unmatched bet (Ref:90216684606) kill results unknown.
15/04/2017 14:18:05: Exception caught while cancelling bet - Exception of type 'BetAngelHelper.APINGException' was thrown.

I wonder if this is due to user error though, with the alterations I had made?

I'll try a few more now I'm back.

Thanks again. I'm used to going 2 steps forward, 3 steps back but this season I'm making a real effort to master things, starting with protecting my bank

[Dallas]

Thanks for the prompt reply Dallas - yes, that makes perfect sense (I did have a lot of markets open trying to make sure I didn't miss any opportunities - typical newbie error I'm sure )

You're right - I was set at 500ms but only seem to be able to come as low as a 200ms refresh rate (not 20ms as you mention) and I am using v1.46.1.

I made some tweaks to my rules before I took my lad to the park during the Spurs game and left them running with 6 markets open (all goals markets) and came back to find no trades have gone through and the following showing in the log:-

15/04/2017 14:18:05: Exception caught while cancelling bet - Exception of type 'BetAngelHelper.APINGException' was thrown.
15/04/2017 14:18:05: WARNING: The Betfair API was unable to process the bet cancellation request. Second attempt activated. (Ref: 90216684606)
15/04/2017 14:18:05: Exception caught while cancelling bet - Exception of type 'BetAngelHelper.APINGException' was thrown.
15/04/2017 14:18:05: WARNING: The Betfair API was unable to process the bet cancellation on the second request. It could cause calculation problems with this fill or kill bet and may leave the bet active in the market. (Ref: 90216684606)
15/04/2017 14:18:05: Unmatched bet (Ref:90216684606) kill results unknown.
15/04/2017 14:18:05: Exception caught while cancelling bet - Exception of type 'BetAngelHelper.APINGException' was thrown.

I wonder if this is due to user error though, with the alterations I had made?

I'll try a few more now I'm back.

Thanks again. I'm used to going 2 steps forward, 3 steps back but this season I'm making a real effort to master things, starting with protecting my bank

The BetAngelHelper.APINGException can be thrown for several reasons including if a timeout occurs and/or Betfair did'nt respond in a reasonable amount of time so in the current situation i would think its most likely to be the case.

However...The latest version is V1.47 so first i would download that
https://www.betangel.com/download/?product=BetAngelPro

Full details of new features are in this blog
https://www.betangel.com/blog_wp/2017/0 ... eleased-2/

To use the faster refresh times ensure you have 'use exchange streaming enabled on your communications tab in the main settings area
https://www.betangel.com/user-guide/sup ... 3D&mw=MzIw

Then with that enabled if you set your guardian refresh rate to 20ms and see how that goes.

Its also worth remembering that you need to have an active connection with the Betfair servers at all times so if you leave your comp unattended make sure it does not go into sleep/hibernation mode etc

[gutuami]

did bf went down for ~7 sec at FFlas 17:15 inplay?

[to75ne]

i did not notice anything but, i could not swear about inplay. pre off no problems here.

[LinusP]

Site maintenance this morning apparently, although its working for me, at least Betdaq send an email

https://twitter.com/BetfairCS/status/854031692830474240

[gutuami]

is bf ok at the moment??

[mjmorris335]

is bf ok at the moment??

No problems here.

Mike

[gutuami]

thanks Mike

[ShaunWhite]

I had a few small problems about an hour ago. Matched bets not showing. I toggled streaming and it was all good again.

[ShaunWhite]

Anyone else getting this? How's it looking for you guys?

[Euler]

Streaming time out there for a little while

[sionascaig]

Getting streaming issues this morning (toggling off seems to fix issue)...

[megarain]

P/L is not updating properly .. am having to close re-open mkt, to get a true P/L.

Be careful.