Log says Back Bet was entirely unmatched at 14:21:52 despite bet being matched entirely on Betfair.
Due to this incorrect log No Offset Bet was placed. This is not a common issue i face, on the same guardian automation file this happens in less than 2% of the market but it does happen. Due to this issue my offset bets dont get placed & my second bet gets placed. Any idea why such error in log?
Also i have a fill or kit bet time of 0.5 seconds but log says at 14:22:03 unmatched bet was killed (same reference number). Why is there a 11 seconds delay in fill or kill bet? Although this is entirely false as my bet was matched in the first instance where on betfair matched time shows 14:21
Copy of my log
17-07-2018 14:21:52: [G_Auto] : $ 4.00 Back bet placed on Under 4.5 Goals at 1.04. Entirely unmatched when it initially reached the market. Ref: **********54 ( Fill or kill bet with 0.5 seconds delay. Offsetting by 1 ticks with greening. )
17-07-2018 14:22:03: [G_Auto] : $ 4 unmatched bet (Ref:**********54) was killed.
Incorrect Log Query
Similar issue of incorrect log entry in another market
17-07-2018 14:28:30: [G_Auto] : $ 4.00 Back bet placed on Under 5.5 Goals at 1.1. Entirely unmatched when it initially reached the market. Ref: **********61 ( Fill or kill bet with 0.5 seconds delay. Offsetting by 1 ticks with greening. )
17-07-2018 14:28:41: [G_Auto] : $ 4 unmatched bet (Ref:**********61) was killed.
Whereas the bet was matched on Betfair
Under 5.5 Goals1.1 $4.00 $0.40
Ref: **********61Matched: 14:28 17-Jul-18
Bets getting matched on Betfair, Log says unmatched, Log says unmatched bet killed, this doesnt activate my offset bets
17-07-2018 14:28:30: [G_Auto] : $ 4.00 Back bet placed on Under 5.5 Goals at 1.1. Entirely unmatched when it initially reached the market. Ref: **********61 ( Fill or kill bet with 0.5 seconds delay. Offsetting by 1 ticks with greening. )
17-07-2018 14:28:41: [G_Auto] : $ 4 unmatched bet (Ref:**********61) was killed.
Whereas the bet was matched on Betfair
Under 5.5 Goals1.1 $4.00 $0.40
Ref: **********61Matched: 14:28 17-Jul-18
Bets getting matched on Betfair, Log says unmatched, Log says unmatched bet killed, this doesnt activate my offset bets
Last edited by hussi.d on Tue Jul 17, 2018 12:21 pm, edited 1 time in total.
This is what should have happened in every other bet
This is correct log. Unmatched Bets. Next Second Killed
17-07-2018 14:31:47: [G_Auto] : $ 4.00 Back bet placed on Under 5.5 Goals at 1.08. Entirely unmatched when it initially reached the market. Ref: **********98 ( Fill or kill bet with 0.5 seconds delay. Offsetting by 1 ticks with greening. )
17-07-2018 14:31:48: [G_Auto] : $ 4 unmatched bet (Ref:**********98) was killed.
This is correct log. Unmatched Bets. Next Second Killed
17-07-2018 14:31:47: [G_Auto] : $ 4.00 Back bet placed on Under 5.5 Goals at 1.08. Entirely unmatched when it initially reached the market. Ref: **********98 ( Fill or kill bet with 0.5 seconds delay. Offsetting by 1 ticks with greening. )
17-07-2018 14:31:48: [G_Auto] : $ 4 unmatched bet (Ref:**********98) was killed.
Last edited by hussi.d on Tue Jul 17, 2018 12:22 pm, edited 1 time in total.
The log only records what happens the moment the bet arrives in the market so your first part is perfectly normal to see
"Entirely unmatched when it initially reached the market. Ref: XXXXXXXXXXX ( Fill or kill bet with 0.5 seconds delay. Offsetting by 1 ticks with greening. )"
However, the 2nd part which is showing up some several seconds later is not right but it looks like it's a refresh/communications issue
What type of refresh rates are you using?
Do you have many markets in guardian?
"Entirely unmatched when it initially reached the market. Ref: XXXXXXXXXXX ( Fill or kill bet with 0.5 seconds delay. Offsetting by 1 ticks with greening. )"
However, the 2nd part which is showing up some several seconds later is not right but it looks like it's a refresh/communications issue
What type of refresh rates are you using?
Do you have many markets in guardian?
Thank You for the ResponseDallas wrote: ↑Tue Jul 17, 2018 11:14 amThe log only records what happens the moment the bet arrives in the market so your first part is perfectly normal to see
"Entirely unmatched when it initially reached the market. Ref: XXXXXXXXXXX ( Fill or kill bet with 0.5 seconds delay. Offsetting by 1 ticks with greening. )"
However, the 2nd part which is showing up some several seconds later is not right but it looks like it's a refresh/communications issue
What type of refresh rates are you using?
Do you have many markets in guardian?
Unlike what the log says, Bet was actually matched the moment it reached the market, Betfair time says 14.21 Matched, if not then it would have been killed with a 0.5 seconds fill or kill bet setting and there would be no matched bet left. And if the bet got matched why didnt the log say bet matched?
Yes second part query solved. Although i use a 20ms refresh rate, it happens due to lot of markets populated on guardian
My query why does the log say bet unmatched & killed even though bet was actually matched
17-07-2018 14:28:30: [G_Auto] : $ 4.00 Back bet placed on Under 5.5 Goals at 1.1. Entirely unmatched when it initially reached the market. Ref: **********61 ( Fill or kill bet with 0.5 seconds delay. Offsetting by 1 ticks with greening. )
17-07-2018 14:28:41: [G_Auto] : $ 4 unmatched bet (Ref:**********61) was killed.
Log says unmatched bet was killed
Whereas the same bet was matched on Betfair so what bet got killed?
Under 5.5 Goals1.1 $4.00 $0.40
Ref: **********61Matched: 14:28 17-Jul-18
17-07-2018 14:28:41: [G_Auto] : $ 4 unmatched bet (Ref:**********61) was killed.
Log says unmatched bet was killed
Whereas the same bet was matched on Betfair so what bet got killed?
Under 5.5 Goals1.1 $4.00 $0.40
Ref: **********61Matched: 14:28 17-Jul-18
Yes due to refresh rate, connectivity issues & number of markets loaded on the guardian there can be delays. But despite of all this the fact which log reports "bet was killed" is not true.
Because bet was actually matched and nothing got killed if bet was matched. So if nothing got killed and bet was filled there should have been an offset bet placed later even with the delay. Why is bet was killed being recorded in the log.
Am I missing something? Kindly help
Because bet was actually matched and nothing got killed if bet was matched. So if nothing got killed and bet was filled there should have been an offset bet placed later even with the delay. Why is bet was killed being recorded in the log.
Am I missing something? Kindly help
Need Help
My offset settings are "Fill or kill bet with 0.5 seconds delay. Offsetting by 10 ticks with greening"
When a Bet is triggered, Log says bet was entirely unmatched when it initially reached the market. Few seconds later log says Unmatched bet was killed.
My Issue is the same bet was actually matched (whereas log incorrectly says unmatched bet was killed) & because BetAngel Log says unmatched bet was killed there was no offset bet placed. How do i resolve this issue.
My Refresh Interval is 20 ms
Restrict Refresh Set to 90 seconds before start so not more than 2-3 matches being refreshed at once.
Broadband Speed is 40 MBps
I have faced this issue of incorrect log being published & offset bet not being triggered in both football & horse racing. Am i Missing something?
My offset settings are "Fill or kill bet with 0.5 seconds delay. Offsetting by 10 ticks with greening"
When a Bet is triggered, Log says bet was entirely unmatched when it initially reached the market. Few seconds later log says Unmatched bet was killed.
My Issue is the same bet was actually matched (whereas log incorrectly says unmatched bet was killed) & because BetAngel Log says unmatched bet was killed there was no offset bet placed. How do i resolve this issue.
My Refresh Interval is 20 ms
Restrict Refresh Set to 90 seconds before start so not more than 2-3 matches being refreshed at once.
Broadband Speed is 40 MBps
I have faced this issue of incorrect log being published & offset bet not being triggered in both football & horse racing. Am i Missing something?
Despite your refresh rate and connection etc the 9-11 sec gaps between your log entries (when it should be a 1 sec gap due to your fill/kill speed) still suggestions something wrong with your connection with BF
Does reverting back to 'Polling' make any difference?
To do this go into
Settings > edit settings > communications
and untick 'use exchange streaming'
Does reverting back to 'Polling' make any difference?
To do this go into
Settings > edit settings > communications
and untick 'use exchange streaming'
7/26/2018 17:14:00: [G_Auto] : $ XX Lay bet placed on 4. Entirely unmatched when it initially reached the market. Ref: *********535 ( Fill or kill bet with 0.5 seconds delay. Offsetting by 10 ticks with greening. )
7/26/2018 17:14:01: [G_Auto] : $ XX unmatched bet (Ref:*********535) was killed.
No Delay in Log
But Log is Incorrect
Bet was actually matched and nothing got killed
Due to this incorrect log Offset Bet did not trigger
What is the reason for this incorrect log. I am not concerned with the delay. Its the log which concerns me. My offset bets don't fire due to this.
7/26/2018 17:14:01: [G_Auto] : $ XX unmatched bet (Ref:*********535) was killed.
No Delay in Log
But Log is Incorrect
Bet was actually matched and nothing got killed
Due to this incorrect log Offset Bet did not trigger
What is the reason for this incorrect log. I am not concerned with the delay. Its the log which concerns me. My offset bets don't fire due to this.
The log has nothing whatsoever to do with placing/triggering bets, it simply writes a note of your activity for you to refer back to later, with no log at all bets would trigger exactly the same.hussi.d wrote: ↑Thu Jul 26, 2018 12:48 pm7/26/2018 17:14:00: [G_Auto] : $ XX Lay bet placed on 4. Entirely unmatched when it initially reached the market. Ref: *********535 ( Fill or kill bet with 0.5 seconds delay. Offsetting by 10 ticks with greening. )
7/26/2018 17:14:01: [G_Auto] : $ XX unmatched bet (Ref:*********535) was killed.
No Delay in Log
But Log is Incorrect
Bet was actually matched and nothing got killed
Due to this incorrect log Offset Bet did not trigger
What is the reason for this incorrect log. I am not concerned with the delay. Its the log which concerns me. My offset bets don't fire due to this.
Did you try polling and slowing the fill/kill time down to 1sec or more as I advised in my last message as your recent log is still showing 0.5 as your fill/kill delay?
Also if your firing in bets every second try slowing this down to 2secs for testing purposes.
Everything still points to the fact your connection is not retrieving the information back from BF fast enough for the settings your using - are you connecting from within the UK or are you overseas?