Triggered Spread loss problem

Hi Folks,
I'm trying to set up a system in the soccer - correct score markets,
that will lay a selection at a certain price, then if the game is getting close
to the end and the bet isn't won, to spread the losses.
I have the lay part of the bet triggering perfectly, but the spread loss is
throwing up some weird problems.
I tried simply, spread loss if the price reaches X, this was unreliable as even after
the score passes the selection, there are still back odds being offered, usually wildly
fluctuating between 1.02 and 1000, the trigger was firing when it shouldn't have.
After this I added a check to see if the score had changed, this was unreliable as
the score doesn't always update correctly. After this I thought I had it cracked by
adding that the selection should be ranked 1, before the spread loss would fire,
but I had one game where something strange happened and even though the score
was past, it ended up ranked 1 and the spread loss fired at odds of 1.02, spending almost £800 to spread the loss of a bet that was winning, thankfully was using test
funds or I'd still be screaming..
Are there any foolproof ways to cover this ?

there are still back odds being offered, usually wildly
fluctuating between 1.02 and 1000, the trigger was firing when it shouldn't have.

Hi
You have answered your own question.
There is not enough liquidity in the market to get a proper value price for the stop-loss, and sometimes there will not be any price at all.
You can try adding a condition to the spread loss trigger to check the gap between best back and best lay prices is reasonable:
and selections trigger expression g_ticks(back_price, lay_price) is less than 10 (or your own preference number of ticks)
but in a market where the prices are so gappy, the condition may never be met.

The other option is to ask the price you want in a back trigger, using a formula to do the calculation for the amount:
http://community.welldonesoft.com/triggered-betting-10/formulas/
but there is no guarantee your back bet will be matched.

Hi, thanks for your reply.
Just to clarify the situation, most of these markets have enough liquidity. Imagine laying the score at half time, let's say 1-0, then the other side equalise bringing the score to 1-1. Bet won, walk away, but there is still odds being offered to back 1-0, im guessing the unmatched lay bets stay active and the trigger eventually fires when they drift into range.
I have now added a trigger to stop refreshing if the score changes. But I've seen the score fail to update before.

Hi
Some other suggestions:

Betfair suspend the markets for goal, red card, penalty. All unmatched bets are cancelled. This condition will wait until the time you specify in seconds after the last suspension. This gives time for the market to re-form. Example below waits 90 seconds after the market last turned in-play:
and selections trigger expression (now_time-last_inplay)/mf_second is equal or greater than 90

Restrict your back price to an acceptable range. For example:
and selections back price is between 1.50 and 30.00

As mentioned previously you can also check the gap between best back and best lay prices. For example:
and selections trigger expression g_ticks(back_price, lay_price) is less than 10

If you feel there is good liquidity, the last condition should do the job, but you can also check the back book%. For example:
and markets back book % is less than 105

And the last idea, if back odds of 1000 are available on 0-0, it is the perfect indicator that the scoreline is higher than 0-0. You can build a condition block to check this:
AND
     selections index is equal to 1
     and selections back price is equal to 1000
AND
     selections index is equal to 2
     and selections back price is equal to 1000

the above should indicate the current score IS NOT 0-0 or 0-1
etc..