BA too fast for its own good...

[Kafkaesque]

Yes, it will mean no further bets until both are matched.

So if your placing more than 1 bet at a time ie, spread betting you won't be able to use it.

Im just looking back at your OP and you said your rearm time was 60 secs - with this there should be no chance of another bet going in with the conditions you're using unless you're using two separate rules to place your opening bets?

This one got away from me, as I had to think about what exactly you meant. Could you expand on what you mean by the last bit with two seperate rules?

The autumation does have several rules (depending on whether or not there's a gap between back and lay prices), although it seems to do it even when it's the same, one rule that's been triggered all the way through. In any case, it seems likely to me that there's a slight issue with the "less than X number of unmatched bets condition" - in the timing of it. Given the test I ran and posted earlier in this thread, where there was a different outcome depending on the setting being equals 0 or less than 1, despite only one simple rule in that test

[Dallas]

Yes, it will mean no further bets until both are matched.

So if your placing more than 1 bet at a time ie, spread betting you won't be able to use it.

Im just looking back at your OP and you said your rearm time was 60 secs - with this there should be no chance of another bet going in with the conditions you're using unless you're using two separate rules to place your opening bets?

This one got away from me, as I had to think about what exactly you meant. Could you expand on what you mean by the last bit with two seperate rules?

The automation does have several rules (depending on whether or not there's a gap between back and lay prices), although it seems to do it even when it's the same, one rule that's been triggered all the way through. In any case, it seems likely to me that there's a slight issue with the "less than X number of unmatched bets condition" - in the timing of it. Given the test I ran and posted earlier in this thread, where there was a different outcome depending on the setting being equals 0 or less than 1, despite only one simple rule in that test

If you have 2 or more rules set to trigger at the same time with same or similar conditions ie, number of unmatched bets <1
They will both trigger simultaneously and your unmatched bets rule will allow it because there are 0 unmatched bets at the time of their trigger.

As Shaun said earlier the matched & unmatched bets need to be retrieved from Betfair before another rule can use them
So a bet gets triggered sent to Betfair and is given a betID and placed in the market as unmatched, BA then needs to receive that unmatched info from Betfair so it knows there is an unmatched bet there.
This, of course, all happens within a second usually (depending on your connection) but if its a little slower then it can and will impact other rules.

If you can try and use a condition that's set locally that way you don't have the wait described above.
Ie, this can be done with signals (as I think Shaun also said earlier in the thread)
or maybe with fill or time since condition etc.

[Dallas]

If I'm right in thinking your from outside the UK then your bets will reach the exchange a little slower, so the matched/unmatched bet info is also a little slower for you so following some of the suggestions in my last post should help stop the double triggers your getting

[Kafkaesque]

Yes, it will mean no further bets until both are matched.

So if your placing more than 1 bet at a time ie, spread betting you won't be able to use it.

Im just looking back at your OP and you said your rearm time was 60 secs - with this there should be no chance of another bet going in with the conditions you're using unless you're using two separate rules to place your opening bets?

This one got away from me, as I had to think about what exactly you meant. Could you expand on what you mean by the last bit with two seperate rules?

The automation does have several rules (depending on whether or not there's a gap between back and lay prices), although it seems to do it even when it's the same, one rule that's been triggered all the way through. In any case, it seems likely to me that there's a slight issue with the "less than X number of unmatched bets condition" - in the timing of it. Given the test I ran and posted earlier in this thread, where there was a different outcome depending on the setting being equals 0 or less than 1, despite only one simple rule in that test

If you have 2 or more rules set to trigger at the same time with same or similar conditions ie, number of unmatched bets <1
They will both trigger simultaneously and your unmatched bets rule will allow it because there are 0 unmatched bets at the time of their trigger.

As Shaun said earlier the matched & unmatched bets need to be retrieved from Betfair before another rule can use them
So a bet gets triggered sent to Betfair and is given a betID and placed in the market as unmatched, BA then needs to receive that unmatched info from Betfair so it knows there is an unmatched bet there.
This, of course, all happens within a second usually (depending on your connection) but if its a little slower then it can and will impact other rules.

If you can try and use a condition that's set locally that way you don't have the wait described above.
Ie, this can be done with signals (as I think Shaun also said earlier in the thread)
or maybe with fill or time since condition etc.

Okay, that makes quite a bit of sense with 2 or more rules. Still though, how does it correlate with the following happening (where there's only one rule)?

Exactly. I'll look into the signal suggestion as a potential solution. However.....this is kinda weird. Set up a simple automation as you suggested. The result being:

21-03-2018 23:24:00: [G_Auto] : k 35.00 Lay bet placed on Petra Martic at 1.38. Entirely unmatched when it initially reached the market. Ref: 119898408501 ( Fill or kill bet with 99999 seconds delay. Offsetting by 1 ticks with greening. )
21-03-2018 23:29:23: [G_Auto] : k 35 of unmatched bet (Ref:119898408501) was filled before remainder was killed.
21-03-2018 23:29:23: [G_Auto] : k 34.75 Back bet placed on Petra Martic at 1.39. Entirely unmatched when it initially reached the market. Ref: 119898604395
21-03-2018 23:29:55: [G_Auto] : k 35.00 Lay bet placed on Petra Martic at 1.37. Entirely unmatched when it initially reached the market. Ref: 119898624460 ( Fill or kill bet with 99999 seconds delay. Offsetting by 1 ticks with greening. )

This was done with unmatched bets equals 0. And the offset bet was placed fine with no extra lay bet. The new lay was only placed when the offset was matched at 23:29:55.

So far so good. On a hunch, I kept the simple automation and only changed to "unmatched bets less than 1" and this happens:

21-03-2018 23:33:22: [G_Auto] : k 35.00 Lay bet placed on Petra Martic at 1.38. Entirely unmatched when it initially reached the market. Ref: 119898787210 ( Fill or kill bet with 99999 seconds delay. Offsetting by 1 ticks with greening. )
22-03-2018 00:00:36: [G_Auto] : k 35.00 Lay bet placed on Petra Martic at 1.37. Entirely unmatched when it initially reached the market. Ref: 119900099751 ( Fill or kill bet with 99999 seconds delay. Offsetting by 1 ticks with greening. )
22-03-2018 00:00:36: [G_Auto] : k 35 of unmatched bet (Ref:119898787210) was filled before remainder was killed.
22-03-2018 00:00:36: [G_Auto] : k 34.75 Back bet placed on Petra Martic at 1.39. Entirely unmatched when it initially reached the market. Ref: 119900100179

So precisely the same issue as I've experienced, despite it being the same market, selection, stakes and my bank being the same. Unless my brain is also getting foggy here late in the day, then surely "equals 0" and "less than 1" is the same (in this context)??? So before messing with signals, is there a potential bug with the " unmatched bets - less than" condition?

As per usual, not trying to be a difficult **** for the sake of it. I would love to clear this up for a number of reasons. Signals are absolutely doing my head in when reading about it. Might be the language barrier catching up, or even me not being all that bright But signals seems to be way less intuitive and not explained as well as the other parts of the software. Also, if the problem is truly elsewhere (ie. in "less than unmatched condition") then adding more moving parts to an automation that's otherwise working well isn't something, I'd fancy before being sure of the value of doing so. Finally, if there is an issue with the specific setting in the condition, I'd think and hope, that BA would like it fixed also.

Thanks for the fast and helpful response as always

[Kafkaesque]

If I'm right in thinking your from outside the UK then your bets will reach the exchange a little slower, so the matched/unmatched bet info is also a little slower for you so following some of the suggestions in my last post should help stop the double triggers your getting

By living in a semi-communistic country, we're already paying a base commission of 6,5%, have a 3 pound min bet, and now you're saying that a bit of water and/or distance between me and the BF base camp is causing trouble......make it stop already

[Dallas]

If you can tell me exactly what part of signals is unclear I could maybe point you at some instructions/examples, but here are few links (which you may or may not have seen)
viewtopic.php?f=37&t=11941
viewtopic.php?f=43&t=11943

It also starts on this page of the user guide
https://www.betangel.com/user-guide/usi ... 3D&mw=MzIw

All the conditions (unmatched bets etc) are working fine and as they should be, until a bet/s is showing in the market and that info is returned by BF they will not be able to see if a bet has been matched or is still unmatched.

Did you try adding the Fill or Kill bet time condition I advised in my first reply?
https://www.betangel.com/user-guide/fil ... 3D&mw=MzIw

That sets locally so won't allow another bet within the time you set, so you could set the condition to
Greater than 2 secs, that will be plenty of time for the bet info to be retrieved so your matched/unmatched conditions can then take over

[Kafkaesque]

If you can tell me exactly what part of signals is unclear I could maybe point you at some instructions/examples, but here are few links (which you may or may not have seen)
viewtopic.php?f=37&t=11941
viewtopic.php?f=43&t=11943

It also starts on this page of the user guide
https://www.betangel.com/user-guide/usi ... 3D&mw=MzIw

All the conditions (unmatched bets etc) are working fine and as they should be, until a bet/s is showing in the market and that info is returned by BF they will not be able to see if a bet has been matched or is still unmatched.

Did you try adding the Fill or Kill bet time condition I advised in my first reply?
https://www.betangel.com/user-guide/fil ... 3D&mw=MzIw

That sets locally so won't allow another bet within the time you set, so you could set the condition to
Greater than 2 secs, that will be plenty of time for the bet info to be retrieved so your matched/unmatched conditions can then take over

As I mentioned in a reply, the fill or kill bet time was a great shout in most cases. However, a rather big part in my strategy requires dripping into the market in many cases. Thus it's really a no go for me.

I'll have a go at signals and see if I can set something up which solves it.

And don't you worry.....although I can't say what gets me, just yet, but I'll give a shout when I get to the part of signals which get me stuck First part was to stop just jumping into trying to have a go, and actually read, as I for the first few frustrating attempts was assuming that the signal needed setting within the existing rules.

Out of sheer curiousity, do you have an official role with BA, or are you a super helpful automation whiz kid? Been meaning to ask forever, and don't think I've ever seen it mentioned on here.

[Kafkaesque]

If you can tell me exactly what part of signals is unclear I could maybe point you at some instructions/examples, but here are few links (which you may or may not have seen)
viewtopic.php?f=37&t=11941
viewtopic.php?f=43&t=11943

It also starts on this page of the user guide
https://www.betangel.com/user-guide/usi ... 3D&mw=MzIw

All the conditions (unmatched bets etc) are working fine and as they should be, until a bet/s is showing in the market and that info is returned by BF they will not be able to see if a bet has been matched or is still unmatched.

Did you try adding the Fill or Kill bet time condition I advised in my first reply?
https://www.betangel.com/user-guide/fil ... 3D&mw=MzIw

That sets locally so won't allow another bet within the time you set, so you could set the condition to
Greater than 2 secs, that will be plenty of time for the bet info to be retrieved so your matched/unmatched conditions can then take over

Okay, that was a bit easier to set up than I expected. Actually quite a bit easier!!!

And at first glance it looks to work an absolute charm. Thanks Dallas (and Shaun, despite me not taking the advice at first )