Tick offset not placed?

[honest guv]

Hi,

I am using the following excel triggers- BACK (or LAY)-TL3-SPC.
At certain times today the tick offset doesn't appear to have been placed. Here is an extract from the log -

16:40:28:657: Processing tick offset for ref:16215746552, ticks:3, fixed odds:0, level profit:True
16:40:28:657: Processing tick offset for ref:16215746553, ticks:3, fixed odds:0, level profit:True
16:40:29:749: Attempted market change, but requests are pending.
16:40:29:796: Processing tick offset for ref:16215746552, ticks:3, fixed odds:0, level profit:True
16:40:29:796: Processing tick offset for ref:16215746553, ticks:3, fixed odds:0, level profit:True
16:40:30:763: retried market:3m3f Hcap Chs
16:40:31:918: Tick offset/stop loss cancelled for ref:16215746552 due to new market loading.
16:40:31:933: Tick offset/stop loss cancelled for ref:16215746553 due to new market loading.
16:40:32:167: Finalising tick offset ref:16215746552
16:40:32:167: Finalising tick offset ref:16215746553
16:40:32:245: Excel first update after market changed.
16:49:48:713: Processing tick offset for ref:16215943340, ticks:3, fixed odds:0, level profit:True

The bet ref 16215746553 was matched (it was a Back bet, but the corresponding offset wasn't placed as far as I can see), although it looks from the log like it should have been cancelled. 16215746552 wasn't matched, but there doesn't seem to be any difference between them in the log.
Is it possible for a bet to be placed, and the market go in play before the offset is placed? Is that what's happened here?

thanks,
Guv

[GaryRussell]

Tick offset/stop loss cancelled for ref:16215746553 due to new market loading.

When it says "cancelled" it actually means it stopped monitoring bet ref 16215746553 with a view to placing the offset when matched because a new market was loaded. It cannot monitor the bet after a new market is loaded. It must have been matched after the new market was loaded. To prevent this problem you should used the CANCEL trigger before changing markets. When it attempts to cancel the bet if it is matched at the same time it will have the opportunity to place the offset bet.

[honest guv]

OK, but I'm using the 'Auto Select Markets - Wait until actual off of preceding race', so shouldn't that prevent any more bets being matched as the market has gone in play?

Is it possible for a bet to be matched milliseconds before the event goes in play, therefore preventing the offset (and in this case SP) bet being placed?

[GaryRussell]

OK, but I'm using the 'Auto Select Markets - Wait until actual off of preceding race', so shouldn't that prevent any more bets being matched as the market has gone in play?

Is it possible for a bet to be matched milliseconds before the event goes in play, therefore preventing the offset (and in this case SP) bet being placed?

It must be getting matched just before it goes in play. I'll investigate because in theory it should be able to catch these before the market changes. I'll get back to you.

[Captain Sensible]

If the bet's close enough to current odds it could easily have been taken in the BSP reconciliation process.

[GaryRussell]

If the bet's close enough to current odds it could easily have been taken in the BSP reconciliation process.

The initial bet is not placed as a keep bet because -SPC is being used so this should not be a an issue.

[Captain Sensible]

I wasn't suggesting the bet's being taken as a keep bet but the BSP takes money from any exchange bets at reconciliation if there's an imbalance between BSP backs and lays in the pool.

The sequence at the off goes

Suspend->Convert BSP keep bets to BSP->BSP reconciliation->Cancel exchange bets with no keep options->inplay.