Where are my bets going?

But even if the qualifying part of the trigger is wrong, at worst it lodges at bet at r_ticks(back_price,1) only IF it is <$4.25 The BSP was 5.48?

hi londolozi
the problem with using formulas in the price box, is the bot will send to betfair the formula figure, NOW if the figure is not within betfairs computer calculations/limits, it will not be classed as a bet, so it will not be cancelled/lapsed or void, because it has not been accepted as a valid bet, so you will see the bot send out a bet, BUT there will be no bet accepted at betfair.
the best way to get around this would be to use 2 triggers.
1 for sp, with the conditions for sp betting
1 for (your set price), with the conditions for none sp betting
in each trigger have a additional condition
for the none sp betting trigger
and trigger sp bets(or whatever you want to name your sp trigger) number of runs is equal to 0
for the sp betting trigger
and trigger none sp bets(or whatever you want to name your none sp trigger) number of runs is equal to 0


mcbee

When betting BSP, and I use a rank condition, what rank is tested, the in_play market?

Eg.
actual_sp < $8
Selections rank = 3

Can I test the BSP market for rank and not the in_play market?
 

hi
that formula should be ok, if you have a trigger condition to make sure that the back price is between the price you want to bet at.
it would be better to have a new trigger to remember or set a variable with the 3rd favourite index number and use the index number for your selection in the betting triggers.

mcbee

Do I use Take SP or Keep for the BSP trigger?

Hi
If you are using a Back trigger action and you want to guarantee your back will be matched at SP at the off, use Take SP, with a condition:
Market's SP is supported
Status: Idle

If you are using a Back trigger action and you want to place a back order at actual_sp after the off:
Action: back
Price: actual_sp
Conditions:
and market's SP is supported
Status: In-Play

If you simply want to back at SP
Action: back at SP
with parameters
Status: Idle

Hi
Log trigger expressions places a heavy load on system resource. I suggested you switch it on in order to determine what the problem was with these:
IF(market_sp=1,actual_sp,r_ticks(back_price,1)) is less than cell_querymarket_id_P(sel_index*3+2)
IF(market_sp=1,actual_sp,r_ticks(back_price,1)) is less than 5.5

If that is working now, switch off logging of trigger expressions, unless you need to check another problem formula.

Hi
For testing and logging trigger expressions, I think if you run just one or two markets and slow down the refresh rate so the logging can keep up with the triggers.

I have a feeling because you are using an Excel link, this interferes with the logging of trigger expressions and vice versa. I seem to remember this has mentioned before.

The only workaround I can think of at the moment is:
to switch off your Excel link temporarily and substitute a value in the formula instead of the Excel value
turn on log trigger expressions
check the log to make sure the formula is working as it should
then turn off log trigger expressions
re-instate the Excel link and run as normal