Offset Bet Not Placed

[Dallas]

If you look at the time difference between of those entries there is a 10 second time difference

19/04/2019 22:04:42: [G_Auto] : £ 2.00 Lay bet placed on 5. Hornblower at 4.3. Entirely unmatched when it initially reached the market. Ref: 161781531553 ( Fill or kill bet with 999 seconds delay. Offsetting by 2 ticks. )
19/04/2019 22:04:52: [G_Auto] : £ 2 unmatched bet (Ref:161781531553) was killed.

When Bet Angel makes a request it gives Betfair 10 seconds to respond after that it has to try and determine whether the bet was actually killed or not based on the information it is given.
In this case, BA is unaware its been matched and instead is believing its been killed so no offset has been placed

When Betfair fail to respond in a timely manner it usually means they are having API issues at the time.

I can see your using streaming from your screenshots so it might be worth trying polling to see if that improves it

[BetScalper]

Thanks Dallas,

Is there a trigger i could build to make sure it doesn't occur or ?

[Dallas]

If you're just placing the 1 bet with offset each selection, you could add the following;

'Set/modify signal rule and set a signal on the selection named 'X'
with the following condition
'Amount of matched bets condition' back bets matched is equal to £2

'Close trade on selection with greening' with the following conditions
'Amount of matched bets condition' lay bets are equal to £0 (you could maybe add another for back bets equal to £2 but I'd prob stick to just the lay condition to start with)

'Signal changed condition'
Signal name 'X' changed between 10 secs and 11 secs (use whatever time you want here)

That will basically tell the close trade rule to trigger 10 secs after the back was matched if the lay bets are still £0

Depending on exactly how your strategy works you may need to change bits of that but that's the general approach I'd use from what I can see your doing

[BetScalper]

Hi,

Seems to be happening allot today. Had 4 offsets not placed on greyhounds.

Turned off streaming but it's still occurring.

Mark

[BetScalper]

There is something seriously going wrong.

20/04/2019 11:36:55: [G_Auto] : £ 2.00 Lay bet placed on 2. Tommys Wolfy at 5.8. Entirely unmatched when it initially reached the market. Ref: 161832542371 ( Fill or kill bet with 999 seconds delay. Offsetting by 2 ticks. )
20/04/2019 11:37:17: [G_Auto] : £ 2.00 Lay bet placed on 3. Only For Faith at 5.6. Entirely unmatched when it initially reached the market. Ref: 161832594309 ( Fill or kill bet with 999 seconds delay. Offsetting by 2 ticks. )
20/04/2019 11:37:17: [G_Auto] : £ 2 of unmatched bet (Ref:161832542371) was filled before remainder was killed.
20/04/2019 11:37:18: [G_Auto] : £ 2.00 Back bet placed on 2. Tommys Wolfy at 6. Entirely unmatched when it initially reached the market. Ref: 161832594609
20/04/2019 11:37:39: [G_Auto] : £ 2 of unmatched bet (Ref:161832594309) was filled before remainder was killed.
20/04/2019 11:37:39: [G_Auto] : Greened up 3. Only For Faith by Backing 1.96 at 5.7
20/04/2019 11:37:39: [G_Auto] : £ 2.00 Back bet placed on 3. Only For Faith at 5.8. Entirely unmatched when it initially reached the market. Ref: 161832646411
20/04/2019 11:37:40: [G_Auto] : Greened up 2. Tommys Wolfy by Laying 0.07 at 5.5
20/04/2019 11:38:23: Guardian has detected that the market is suspended

[Dallas]

I assume the current connection your using is a wired one?

Do you have another connection you can try for a while even if it's a 4g or wifi hotspot?
with the number of errors, you're getting if it was the API others would have spotted it too by now

[Dabbla]

Are you using batches ? I think that can lead to offsets not being placed. I just cant remember why !!

[Dallas]

Couple of other things to check

It looks like your using some sort of restrict refresh or are switching to the market your automation is running on if that's correct can you confirm which and the settings?

Also, can you post a screenshot of your Communication settings that you're using?

And finally when you use polling what sort of responsiveness numbers are you getting in the bottom right corner near where your username is?
and are these pretty stable or do they fluctuate a lot?

[BetScalper]

Its a wired connection.

[foxwood]

As I read the log, in the same cycle at 11:37:39, BA discovered your lay was fully matched, BA executed your green up rule, BA placed the offset for the fully matched lay.

Either there is an issue with your green up logic or BA has an issue - would have thought BA logic should see the matched bet and place the offset THEN execute your rules - think it would have worked properly in that case ?

[Dallas]

Its a wired connection.

I can see your Dynamic tuner is still in its default 10 position

you could try a smaller value of 5. That won't stop any connection issues, but it'll force Bet Angel to abandon the call more quickly and make a new request of the same information.

If that doesn't work it might be worth exporting your 'settings' profile and sending it into support with your automation file for them to try and recreate it

[Bet Angel]

As I read the log, in the same cycle at 11:37:39, BA discovered your lay was fully matched, BA executed your green up rule, BA placed the offset for the fully matched lay.

Yes, that's how we read it too. The green-up calculation was placed based on the matched bets at that moment in time, at the same time as the offset bet was in transit to betfair, which matched a couple of seconds later causing the P&L as displayed. However, the bet that needed to be offset was filled 16 seconds earlier, so should have offset sooner than it did. That's why we think the calls to get matched bets timed-out during that period.

A safeguard to this would be to issue multiple greening rules (perhaps five seconds apart), that way even if the first one 'crossed in the post', the second call would tidy-up.

[BetScalper]

As I read the log, in the same cycle at 11:37:39, BA discovered your lay was fully matched, BA executed your green up rule, BA placed the offset for the fully matched lay.

Yes, that's how we read it too. The green-up calculation was placed based on the matched bets at that moment in time, at the same time as the offset bet was in transit to betfair, which matched a couple of seconds later causing the P&L as displayed. However, the bet that needed to be offset was filled 16 seconds earlier, so should have offset sooner than it did. That's why we think the calls to get matched bets timed-out during that period.

A safeguard to this would be to issue multiple greening rules (perhaps five seconds apart), that way even if the first one 'crossed in the post', the second call would tidy-up.

That’s the strange thing as I have a greenup rule to trigger every 5 seconds 4 times.

[Bet Angel]

Are you auto-switching the main screen into each market, or just using the Guardian cycle to refresh information? If only using the Guardian cycle, then try auto-switching to see if it makes any difference. It'll also help capture the whole day's activity into one log, that you can then send into support for us to work through.
Regarding your other missing matched bets display in the beta thread, we've tested that all afternoon and it's worked faultlessly both streaming and non-streaming. The issues are probably related, but we can't explain what you're seeing at the moment. Hopefully the full log will help.

[foxwood]

As I read the log, in the same cycle at 11:37:39, BA discovered your lay was fully matched, BA executed your green up rule, BA placed the offset for the fully matched lay.

Yes, that's how we read it too. The green-up calculation was placed based on the matched bets at that moment in time, at the same time as the offset bet was in transit to betfair, which matched a couple of seconds later causing the P&L as displayed. However, the bet that needed to be offset was filled 16 seconds earlier, so should have offset sooner than it did. That's why we think the calls to get matched bets timed-out during that period.

A safeguard to this would be to issue multiple greening rules (perhaps five seconds apart), that way even if the first one 'crossed in the post', the second call would tidy-up.

Didn't pick up that refresh rate was 200ms so the three events probably not at the same time - I was thinking had 1 second refresh rate and all happened together.

Might be worth change to logging in a future release to also show milliseconds on the time to help analyse issues ?