Automation logs filled with errors

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
zanpo
Posts: 41
Joined: Wed Jul 06, 2016 3:05 pm

I am using Betangel in practice mode for testing a method, all goes well when all of a sudden, in one of the horse racings for the day, I got this error in my logs, error witch continues for the rest of the races, and the only way to get read of it is to close Betangel completely and open it again. So...I am thinking is something wrong with Betangel, not the Betfair API, right?

Here are the log entries for the race Nottingham 17:35 (I am GMT+2 here), I only copied the essential parts:

Here the bot was supposed to green up, the race starts at 19:35, and my automation is set to run 30 sec after event goes in play, with a final green up:

Code: Select all

02/08/2016 19:35:29: [G_Auto] :  Automation Signal for Singing Sands: unmatched = 1
02/08/2016 19:35:29: [G_Auto] :  Cancelling bets 17280  17281  
02/08/2016 19:35:29: [G_Auto] :  Greened up Singing Sands by Backing 9.90 at 2.06
02/08/2016 19:35:29: [G_Auto] :  Automation Signal for Singing Sands: All Signals Cleared
02/08/2016 19:35:29: [G_Auto] :  € 10.00 Lay bet placed on Singing Sands at 2.04.  Entirely unmatched when it initially reached the market.   Ref: 17283          ( Fill or kill bet with 5 seconds delay.  Offsetting by 1 ticks.   )
02/08/2016 19:35:29: [G_Auto] :  Automation Signal for Gilgamesh: All Signals Cleared
02/08/2016 19:35:29: [G_Auto] :  € 10.00 Lay bet placed on Gilgamesh at 4.1.  Entirely unmatched when it initially reached the market.   Ref: 17284          ( Fill or kill bet with 5 seconds delay.  Offsetting by 1 ticks.   )
02/08/2016 19:35:30: [G_Auto] :  Automation Signal for Singing Sands: unmatched = 1
02/08/2016 19:35:30: [G_Auto] :  Cancelling bets 17283  17284
But after that these lines appear, for which I have no idea and no explanation (here is just a part, there are many more):

Code: Select all

02/08/2016 19:35:35: [G_Auto] :  € 10 unmatched bet (Ref:17161) was killed.
02/08/2016 19:35:55: [G_Auto] :  € 10 unmatched bet (Ref:17152) was killed.
02/08/2016 19:36:15: [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: 17147)
02/08/2016 19:36:15: [G_Auto] :  Unmatched bet (Ref:17147)  kill results unknown.
02/08/2016 19:36:35: [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: 17142)
02/08/2016 19:36:35: [G_Auto] :  Unmatched bet (Ref:17142)  kill results unknown.
And they continue to go with these lines (at 19:40, 5 minutes after the in play):

Code: Select all

02/08/2016 19:40:36: [G_Auto] :  € 10 of unmatched bet (Ref:17277) was filled before remainder was killed.
02/08/2016 19:40:36: [G_Auto] :  € 10.00 Back bet placed on Singing Sands at 2.06. Fully matched at 2.12.  Ref: 17586
02/08/2016 19:40:36: [G_Auto] :  € 10 of unmatched bet (Ref:17272) was filled before remainder was killed.
02/08/2016 19:40:36: [G_Auto] :  € 10.00 Back bet placed on Singing Sands at 2.08. Fully matched at 2.12.  Ref: 17588
02/08/2016 19:40:36: [G_Auto] :  € 10 of unmatched bet (Ref:17270) was filled before remainder was killed.
02/08/2016 19:40:36: [G_Auto] :  € 10 of unmatched bet (Ref:17267) was filled before remainder was killed.
02/08/2016 19:40:36: [G_Auto] :  € 10.00 Back bet placed on Singing Sands at 2.12. Fully matched at 2.12.  Ref: 17590

02/08/2016 19:40:36: [G_Auto] :  € 10.00 Back bet placed on Gilgamesh at 4.2. Entirely unmatched when it initially reached the market.   Ref: 17600
02/08/2016 19:40:36: [G_Auto] :  € 10 of unmatched bet (Ref:17233) was filled before remainder was killed.
02/08/2016 19:40:36: [G_Auto] :  € 10.00 Back bet placed on Singing Sands at 1.93. Fully matched at 2.12.  Ref: 17601
02/08/2016 19:40:36: [G_Auto] :  € 10 of unmatched bet (Ref:17232) was filled before remainder was killed.
02/08/2016 19:40:36: [G_Auto] :  € 10.00 Back bet placed on Singing Sands at 1.94. Fully matched at 2.12.  Ref: 17602
02/08/2016 19:40:36: [G_Auto] :  € 10 of unmatched bet (Ref:17231) was filled before remainder was killed.
02/08/2016 19:40:36: [G_Auto] :  € 10.00 Back bet placed on Singing Sands at 2.02. Fully matched at 2.12.  Ref: 17603
02/08/2016 19:40:36: [G_Auto] :  € 10.00 Back bet placed on Gilgamesh at 4.4. Entirely unmatched when it initially reached the market.   Ref: 17604

Ok after this, here the bot detects in play:

Code: Select all

02/08/2016 19:41:00:  Guardian has detected that the market is in-play
02/08/2016 19:41:00:  Guardian has detected that the market is suspended


But all of a sudden, these lines come up, and I have no explication for them. I also have restrict refresh in Guardian 60 seconds after start time, so why is the bot doing this?

Code: Select all

02/08/2016 19:52:31: [G_Auto] :  WARNING: The Betfair API was unable to process the bet cancellation request.  Second attempt activated. (Ref: 17283)
02/08/2016 19:52:31: [G_Auto] :  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: 17283)
02/08/2016 19:52:31: [G_Auto] :  Unmatched bet (Ref:17283)  kill results unknown.
02/08/2016 19:52:31: [G_Auto] :  WARNING: The Betfair API was unable to process the bet cancellation request.  Second attempt activated. (Ref: 17284)
02/08/2016 19:52:31: [G_Auto] :  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: 17284)
02/08/2016 19:52:31: [G_Auto] :  Unmatched bet (Ref:17284)  kill results unknown.
And goes on until this final line of the log entry:

Code: Select all

02/08/2016 19:52:31: [G_Auto] :  WARNING: The Betfair API was unable to process the bet cancellation request.  Second attempt activated. (Ref: 17217)
02/08/2016 19:52:31: [G_Auto] :  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: 17217)
02/08/2016 19:52:31: [G_Auto] :  Unmatched bet (Ref:17217)  kill results unknown.

Let's take bet with ref. 17283 and 17284 . In the log this bet has these lines:

Code: Select all

02/08/2016 19:35:29: [G_Auto] :  Automation Signal for Singing Sands: All Signals Cleared
02/08/2016 19:35:29: [G_Auto] :  € 10.00 Lay bet placed on Singing Sands at 2.04.  Entirely unmatched when it initially reached the market.   Ref: 17283          ( Fill or kill bet with 5 seconds delay.  Offsetting by 1 ticks.   )
02/08/2016 19:35:29: [G_Auto] :  Automation Signal for Gilgamesh: All Signals Cleared
02/08/2016 19:35:29: [G_Auto] :  € 10.00 Lay bet placed on Gilgamesh at 4.1.  Entirely unmatched when it initially reached the market.   Ref: 17284          ( Fill or kill bet with 5 seconds delay.  Offsetting by 1 ticks.   )
02/08/2016 19:35:30: [G_Auto] :  Automation Signal for Singing Sands: unmatched = 1
02/08/2016 19:35:30: [G_Auto] :  Cancelling bets 17283  17284

In settings -> communication tab, "Matched & unmatched bets" is set to the lowest, 200 ms.

I have no idea what is going on. Because after this error, all the races are messed up, the automation doesn't respect what it is supposed to do....the only solution is to close Betangel and open it again.

Please help, this happens on a daily basis (strangely only for horse racings, not for greyhounds, using the same automation file) I am afraid to go like this in live mode, I have no idea what can happen.
Top
Post Reply

Return to “Bet Angel - Automation”