Matched Bets not Showing

[Dipstick]

Dallas
Re my earlier post. I have downloaded it and tried again. As I mentioned, all I have done is added a volume condition of over £5k to the two lay bets and nothing else. So again, the "red out" didn't trigger- presumably at 8.52. What am I doing wrong (I still have streaming on at 20ms refresh)?

Dipstick

16/12/2018 08:05:46: Guardian has detected that the market is in-play
16/12/2018 08:05:46: Guardian has detected that the market is suspended
16/12/2018 08:05:46: Guardian has detected that the market is now unsuspended
16/12/2018 08:32:05: [G_Auto] : £ 10.00 Lay bet placed on Melbourne City at 1.92. Entirely unmatched when it initially reached the market. Ref: 148219930358 ( Opening Stop at 3 ticks. Place stop at 5 ticks )
16/12/2018 08:37:11: Stop triggered. Modify bet 148219930358 from 10 @ 1.92 to 10 @ 1.97 New Ref: 148220156382
16/12/2018 08:52:07: [G_Auto] : An error occurred while cancelling bets: The entire order has been rejected.
16/12/2018 08:52:07: [G_Auto] : Cancelling bets 148220156382
16/12/2018 09:58:02: Guardian has detected that the market is suspended

[Dallas]

Dallas
Re my earlier post. I have downloaded it and tried again. As I mentioned, all I have done is added a volume condition of over £5k to the two lay bets and nothing else. So again, the "red out" didn't trigger- presumably at 8.52. What am I doing wrong (I still have streaming on at 20ms refresh)?

Dipstick

16/12/2018 08:05:46: Guardian has detected that the market is in-play
16/12/2018 08:05:46: Guardian has detected that the market is suspended
16/12/2018 08:05:46: Guardian has detected that the market is now unsuspended
16/12/2018 08:32:05: [G_Auto] : £ 10.00 Lay bet placed on Melbourne City at 1.92. Entirely unmatched when it initially reached the market. Ref: 148219930358 ( Opening Stop at 3 ticks. Place stop at 5 ticks )
16/12/2018 08:37:11: Stop triggered. Modify bet 148219930358 from 10 @ 1.92 to 10 @ 1.97 New Ref: 148220156382
16/12/2018 08:52:07: [G_Auto] : An error occurred while cancelling bets: The entire order has been rejected.
16/12/2018 08:52:07: [G_Auto] : Cancelling bets 148220156382
16/12/2018 09:58:02: Guardian has detected that the market is suspended

Can you see from your matched bets if that was/wasn't the case and if so what the exact time and price the bet was matched at?

What should happen is if the open lay isn't matched and the price bounces out 3 ticks it's moved and placed 5 ticks higher to try and get matched, what it looks like has happened is that occurred and the was moved and was either matched or not but the slow drift out took longer than 20mins by which time the 20min green up window had elapsed.
In other words, the price more or less flatlined above where the lay was placed for over 20mins resulting it in not being matched until over 20mins later.

If that is the case that would be a very rare event but as its happened a few times for you it might be worth making a small change, there are several things that could be done which i'll list depending on the time of the matched bets you got

[Dipstick]

Dallas
This gets stranger, The bot triggered a total of 15 times. In all cases, only the opening trade was fired. But in 11 of the matches, BetAngel does not show any matched bets (but I do get the same audit log as above) - that is an opening bet followed by a cancelled bet.

In 4 of the cases, I get the same but Bet Angel does show the matched bet. This is generally timed at about 20 secs after the submission (eg 12.03.36 fire/ 12.04.02 log on to the matched bets screen).

I have then looked at my system clock and I have noticed that my laptop clock is running about 22seconds behind realtime - it refuses to recalibrate to actual time even though I have ticked the box in settings. I have seen this before. Could this be the cause?

Dipstick

[Dallas]

Dallas
This gets stranger, The bot triggered a total of 15 times. In all cases, only the opening trade was fired. But in 11 of the matches, BetAngel does not show any matched bets (but I do get the same audit log as above) - that is an opening bet followed by a cancelled bet.

In 4 of the cases, I get the same but Bet Angel does show the matched bet. This is generally timed at about 20 secs after the submission (eg 12.03.36 fire/ 12.04.02 log on to the matched bets screen).

I have then looked at my system clock and I have noticed that my laptop clock is running about 22seconds behind realtime - it refuses to recalibrate to actual time even though I have ticked the box in settings. I have seen this before. Could this be the cause?

Dipstick

Have you synced your PC to internet time?
Its done slightly different depending on your version of windows but once you have your 'Time and date' open you should see a tab or option for 'internet' time where you can choose an internet server to sync to.

I don't think it should cause any issues to the rules but best to try and solve this first before looking at other things as I've had no issues with testing and no one else is having problems either, also I have been using a similar variation of this for some time.

[Hobsom]

I had some issues with my PC time constantly going out of sync some time ago, and I eventually found that the PC was running an overclocking program that changed the speed of the clock process within the OS. There were also overclocking settings in the BIOS. The time sync problem was fully resolved by removing all of the overclocking settings.
This may not help at all, but I thought I'd mention it just in case.

[Dipstick]

Thanks for this. Tried synching this morning. Firstly it says that An error occurred with synchrnisning with "time.windows.com" because the timeout period expired. and then it said that it had synchronised. It is telling me that it will try and synchronise again at 3.22 this afternoon - so I will see if that works.

I will also close down BetAngel and reopen again - as I have found that automation doesn't work if I have changed the time

[BetScalper]

Thanks for this. Tried synching this morning. Firstly it says that An error occurred with synchrnisning with "time.windows.com" because the timeout period expired. and then it said that it had synchronised. It is telling me that it will try and synchronise again at 3.22 this afternoon - so I will see if that works.

I will also close down BetAngel and reopen again - as I have found that automation doesn't work if I have changed the time

Your not running VMware are you ?

[Dipstick]

Betscalper - no, I am not (knowingly) running VMWare (not techie enough for that)

Dallas - time synching isnt the issue - it is the "greenup" bit. The automation kicked in and fired at the 20minute mark. I tried again on the Boro vs Burton game. The lay bet was triggered at 20:52.37 when Burton scored. The "green up" triggered at 21:12.41 as epected when no one scored. But then i got the error message:

18/12/2018 20:52:43: [G_Auto] : £ 10.00 Lay bet placed on Burton at 2.36. Entirely unmatched when it initially reached the market. Ref: 148451183522 ( Opening Stop at 3 ticks. Place stop at 5 ticks )
18/12/2018 21:12:41: [G_Auto] : An error occurred while cancelling bets: The entire order has been rejected.
18/12/2018 21:12:41: [G_Auto] : Cancelling bets 148451183522
18/12/2018 21:42:45: Guardian has detected that the market is suspended

Dipstick

[Dallas]

Dallas - time synching isnt the issue - it is the "greenup" bit. The automation kicked in and fired at the 20minute mark. I tried again on the Boro vs Burton game. The lay bet was triggered at 20:52.37 when Burton scored. The "green up" triggered at 21:12.41 as epected when no one scored. But then i got the error message:

18/12/2018 20:52:43: [G_Auto] : £ 10.00 Lay bet placed on Burton at 2.36. Entirely unmatched when it initially reached the market. Ref: 148451183522 ( Opening Stop at 3 ticks. Place stop at 5 ticks )
18/12/2018 21:12:41: [G_Auto] : An error occurred while cancelling bets: The entire order has been rejected.
18/12/2018 21:12:41: [G_Auto] : Cancelling bets 148451183522
18/12/2018 21:42:45: Guardian has detected that the market is suspended

Dipstick

So was the lay bet actually matched and if so at what time? the log is basically saying it tried to cancel the lay but was rejected which suggests it's been matched but it is also showing it couldn't be cancelled.

Also if you're not already using polling try reverting back to that just to rule out a streaming issue,

[Dipstick]

Dallas

Nothing shows on BetAngel (ie there is no recorded matched bet info). On the Betfair site, it shows that the bet was placed at 20.52 and matched at 20.53.

Dipstick

[Dallas]

Dallas

Nothing shows on BetAngel (ie there is no recorded matched bet info). On the Betfair site, it shows that the bet was placed at 20.52 and matched at 20.53.

Dipstick

Did you check that before logging out of BA or did you log back in at a later time to check?

If it was before logging out ie, you checked during or just after the match and it wasn't showing in BA then it sounds like for whatever reason BA isn't retrieving the latest bet status info which is then causing issues with the greening rule

Did you try reverting back to polling and trying the file again?
If your unable to retrieve the latest bet status I have a feeling its to do with streaming so want to eliminate that first

[Dipstick]

Dallas

Yes, I think it's a problem retrieving data from Betfair - i have another automation bot which had similar responses - ie the cancellation bet on greeing didn't work. I used the "close trade on selection with greening" option. Have switched to straightforward greening instead to see if that works

[Dipstick]

Dallas

Closed BA and logged back in again as proposed

Tried Hoffenheim vs Mainz yesterday and got same thing happening. Tried a back bet with offsetting this time

23/12/2018 16:59:00: [G_Auto] : £ 10.00 Back bet placed on Under 3.5 Goals at 1.77. Fully matched at 1.77. Ref: 148929730221 ( Offsetting by 14% [A] with greening. )
23/12/2018 16:59:00: [G_Auto] : £ 11.64 Lay bet placed on Under 3.5 Goals at 1.52. Entirely unmatched when it initially reached the market. Ref: 148929730335
23/12/2018 16:59:15: [G_Auto] : Modify bet persistence 148929730335 from 'Cancel' to 'Keep'

23/12/2018 16:59:53: Guardian has detected that the market is in-play
23/12/2018 16:59:53: Guardian has detected that the market is suspended
23/12/2018 16:59:55: Guardian has detected that the market is now unsuspended
23/12/2018 17:11:47: [G_Auto] : Cancelling bets 148929730335
23/12/2018 17:11:52: [G_Auto] : Greened up Under 3.5 Goals by Laying 7.90 at 2.24
23/12/2018 17:16:54: [G_Auto] An error occurred while cancelling bets: The entire order has been rejected.
23/12/2018 17:16:54: [G_Auto] : Cancelling bets 148930830712
23/12/2018 17:16:59: [G_Auto] : Greened up Under 3.5 Goals by Laying 3.77 at 4.7
23/12/2018 18:53:24: Guardian has detected that the market is suspended

The problem is that the green up (well red up) did actually work at 17:12 so there should have been no position outstanding at 17:17 when it then submitted another green up at 17:17 which also worked. Yet, BA only showed the single back bet at the start.

Note that I have the "restricted refresh" on as well (from 10minutes before) but it seems to be refreshing every game in the future as well. I would hope that might solve the polling issue but it doesn't

Dipstick

[Dallas]

Which are you currently using streaming or polling?

And have you tried reverting to polling if on streaming?

[Dipstick]

Dallas

Yes, I was on streaming. have switched to a polling setting I have (sillyquestion - i presume that polling is not streaming (want to get the terminilogy right)).
Also, I note that my clock was out by 10 seconds again so I have reset that - the auto-synchronisation is just not working using the Internet time setting....

Am trying it on a couple of israeli matches that kick off in 10mins

Dipstick