Dealing with late scratchings?

[rinconpaul]

There's one occurrence that is awfully hard to deal with, and that's a late scratching and the effect it has on prices. Case in point Aqueduct R8. My bot is programmed to trigger at the official start time. 21 secs out, the market is suspended (I can only reason it was for a late scratching, and then 17 secs out unsuspended. The Back prices take a tumble and at the official start there are now 5 selections sub $1.60 and the remaining three, sub $6. However the Lay prices range from $2.80 - $67.20. Any code using a Lay - Back $ spread is stuffed, and my bot fires off 4 Lay bets.


My lucky day though none of them won...phew! Any ideas on a code to insure against this occurrence, apart from not using spreads as triggers?

[spreadbetting]

You need to start checking the overrounds to see if there's a decently formed book i.e. something like a 96% back 104% lay market or whatever you consider acceptable to back into. Remember to take into account runners without quoted odds too as you can never add enough criteria to unattended bots. Missing the odd race here and there cos your criteria is too tight is much better than dumping your bank and there's plenty of races so missing some shouldn't be any problem.

Or start looking to time your bots as close to the actual off as possible which is never too easy with US racing which can go off before the advertised off on occasions. I used to link my bots to sites like https://classic.ebetusa.com/racing_menus/next-race.html which give a better idea of the off time than the simple official start time for botting.

[Rinoa]

If using Guardian Automation, employing the 'Unsuspended Time Condition' would prevent that from happening.

[rinconpaul]

Some very worthwhile replies and thinking outside the box. Appreciate that.