automation advice please

[cmuddle]

I've often found that automation fires in a second bet at the same as the first bet is matched. It seems to fire in that second bet, before the offset is placed, as there's a temporary gap with the unmatched bets on the selection being zero. I've worked with various settings and the refresh rates, but have been unable to come up with solution which works anywhere close to all the time.

When trading in-play to account for the delay time If you use a 'fill or kill bet time condition' is greater than 2 secs (or any time longer than the IP delay) that will avoid any bets being triggered whilst waiting for the offset being placed

I have problems trading with back and lay in-play with guardian offset bets which do not trigger. The bet is placed but the offset bet either does not trigger or disappears.
Does it have to do also with the 2 secs fill or kill ? My automation is set to 2 secs fill or kill.
Or is it something else?

[ShaunWhite]

If you're backing pre and you need your offset to remain in-play. You'll need to have a rule that changes the status of your unmatched trades to 'Keep' otherwise BF will cancel them.

And yes, 2s fill/kill is not enough as bets are delayed by at least 2s in-play by BF

[Dipstick]

Have had an issue twice with an automation rule this morning, Can anyone help please - possibly Dallas, but trying to see if anyone else has seen the same issue.

I have a green up rule which has a "Not in play" indicator as well as a "don't fire until 30 secs after unsuspension" condition. But twice today, the rule has kicked in immediately after going in play (and its related suspension). It kicks in 1 second after and I think it might be a timing issue on the telecomms that I can do nothing about. Can anyone help me stop this please. Log details below:

15/12/2017 08:38:20: Guardian has detected that the market is in-play
15/12/2017 08:38:20: Guardian has detected that the market is suspended
15/12/2017 08:38:21: Guardian has detected that the market is now unsuspended
15/12/2017 08:38:21: [G_Auto] : Greened up 3. Backbench Blues by Laying 1.76 at 24
15/12/2017 08:38:21: [G_Auto] : Greened up 6. Toni May by Laying 13.39 at 3.95
15/12/2017 08:38:22: [G_Auto] : Greened up 2. Dharmony by Backing 0.73 at 3.25
15/12/2017 08:40:08: Guardian has detected that the market is suspended

Thanks

Dipstick

[Dallas]

Have had an issue twice with an automation rule this morning, Can anyone help please - possibly Dallas, but trying to see if anyone else has seen the same issue.

I have a green up rule which has a "Not in play" indicator as well as a "don't fire until 30 secs after unsuspension" condition. But twice today, the rule has kicked in immediately after going in play (and its related suspension). It kicks in 1 second after and I think it might be a timing issue on the telecomms that I can do nothing about. Can anyone help me stop this please. Log details below:

15/12/2017 08:38:20: Guardian has detected that the market is in-play
15/12/2017 08:38:20: Guardian has detected that the market is suspended
15/12/2017 08:38:21: Guardian has detected that the market is now unsuspended
15/12/2017 08:38:21: [G_Auto] : Greened up 3. Backbench Blues by Laying 1.76 at 24
15/12/2017 08:38:21: [G_Auto] : Greened up 6. Toni May by Laying 13.39 at 3.95
15/12/2017 08:38:22: [G_Auto] : Greened up 2. Dharmony by Backing 0.73 at 3.25
15/12/2017 08:40:08: Guardian has detected that the market is suspended

Thanks

Dipstick

Except for timing issues i cant see anything else that would cause it. Can you post some screenshots of the green up rule settings you were using, (general and conditions tabs etc)