automation newbie question

We were all new to Bet Angel once. Ask any question you like here and fellow forum members promise not to laugh. Betfair trading made simple.
Post Reply
User avatar
brimson25
Posts: 504
Joined: Sat Apr 08, 2017 11:42 am

Hello. I am not a newbie, but I am to automation. I've been messing around was a a lay to back horse bot.

I ended up making more money than I expected on the 15.20 at Warwick, where the bot laid Present Storm, but did not offset. That's great for this race, but worries me more generally because I don't understand what happened and I could have easily lost money.

I have run this bot about 50 times and this is the first time this has happened. I am sure I must seem very dense asking asking this, but does this log make it clear what happened? (ie. why offsetting bet did not get placed?)

It seems to say my issue is the refresh rate, but I do not understand why this is a problematic on this race and not the others.

Grateful for any comments, but probably fully deserving of any mockery that comes my way!

Here is the log:

9/2021 15:21:10: Guardian has detected that the market is in-play
21/09/2021 15:21:10: Guardian has detected that the market is suspended
21/09/2021 15:22:15: [G_Auto] : Store Value for Present Storm: 10 = 5.5 - 10% = 5
21/09/2021 15:22:15: [G_Auto] : Store Value for Present Storm: 10 = 5.5 - 10% = 5
21/09/2021 15:22:15: Guardian has detected that the market is now unsuspended
21/09/2021 15:22:16: [G_Auto] : £ 4.35 Lay bet placed on Present Storm at 3.3. Entirely unmatched when it initially reached the market. Ref: 244878425035 ( Fill or kill bet with 20 seconds delay. Offsetting by 26% [A] with greening. Trailing Stop at 50% [A]. Place stop at 56% [A] )
21/09/2021 15:22:16: [G_Auto] : £ 8.70 Lay bet placed on Present Storm at 3.3. £ 1.9 matched at 3.3 £ 6.8 unmatched when it initially reached the market. Ref: 244878425032 ( Fill or kill bet with 20 seconds delay. Offsetting by 12 ticks with greening. Trailing Stop at 50 ticks. Place stop at 56 ticks )
21/09/2021 15:22: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: 244878425032)
21/09/2021 15:22:46: [G_Auto] : Unmatched bet (Ref:244878425032) kill results unknown.
21/09/2021 15:22:56: [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: 244878425035)
21/09/2021 15:22:56: [G_Auto] : Unmatched bet (Ref:244878425035) kill results unknown.
21/09/2021 15:25:27: Guardian has detected that the market is suspended
User avatar
Dallas
Posts: 22726
Joined: Sun Aug 09, 2015 10:57 pm
Location: Working From Home

Yeah its basically down to to your refresh speed, it wouldn't be a regular occurrence as you've noticed but if you are refreshing a lot of markets and your refresh speed is slow there will be times when this happens

This post explains more about how the refresh rate in Guardian effects your automation and shows where to make changes to get the perfect results
viewtopic.php?f=37&t=11491
User avatar
brimson25
Posts: 504
Joined: Sat Apr 08, 2017 11:42 am

Thanks very much Dallas.
Post Reply

Return to “Bet Angel for newbies / Getting started”