Author Topic: Trigger conditions not met consistently  (Read 772 times)

Tags:
  • All members
  • Posts: 92
Trigger conditions not met consistently
« on: 19 Jun 2022, 08:37 »
I have a trigger set as per back_log (below) to back a horse if the price has risen in the last 10 minutes. The 10 min price is captured using remember.

The problem is that sometimes the condition is met, and sometimes it isn't - even though it should be.

The log in this example shows the condition to be FALSE, even though the price was obviously higher at the time (compare the prices in 10_price (10 mins before the off) and 1_price (1 min before) captured by the same triggers (the prices in the text files are back and lay respectively)).

What could be causing it to miss the valid condition? Like I said, sometimes it works, sometimes it doesn't.

  • Tim Vetrov
  • Administrator
  • Posts: 4655
  • Gender: Male
*
Re: Trigger conditions not met consistently
« Reply #1 on: 20 Jun 2022, 18:27 »
What's the condition looks like?
It seems 10minsprices_meeting_id_back_price was parsed from something.
Proud to be 🇺🇦
I'm happy to help Monday - Friday, 08:00-18:00 GMT
Буду рад помочь с понедельника по пятницу, 08:00-18:00 GMT

  • All members
  • Posts: 92
Re: Trigger conditions not met consistently
« Reply #2 on: 21 Jun 2022, 20:46 »
Here are the triggers:

  • Tim Vetrov
  • Administrator
  • Posts: 4655
  • Gender: Male
*
Re: Trigger conditions not met consistently
« Reply #3 on: 22 Jun 2022, 07:31 »
Thank you.
First of all please set the first trigger to execute once per market as you remember the whole market.
The second one could be set to "once per selection" if you need to place bet on each selection whenever it meets the condition. So it could place several bets on the same market but never on the same selection.
Why do you need "meeting_id" bind? As I see both triggers work on the same market, so 10minsprice_market_id would be enough.
By the way you can use pdiff_9 trigger variable comparing with 0 to get rid of the "remember" trigger at all:

Code: [Select]
Selection's Trigger Expression pdiff_9 is greater than 0
Proud to be 🇺🇦
I'm happy to help Monday - Friday, 08:00-18:00 GMT
Буду рад помочь с понедельника по пятницу, 08:00-18:00 GMT

  • All members
  • Posts: 92
Re: Trigger conditions not met consistently
« Reply #4 on: 22 Jun 2022, 12:45 »
Thanks Tim, I'll give these suggestions a go.

I added meeting_id after I realised the original trigger wasn't working - I thought it may have become confused with multiple markets running simultaneously.

  • Tim Vetrov
  • Administrator
  • Posts: 4655
  • Gender: Male
*
Re: Trigger conditions not met consistently
« Reply #5 on: 22 Jun 2022, 12:48 »
The market_id is enough.
Proud to be 🇺🇦
I'm happy to help Monday - Friday, 08:00-18:00 GMT
Буду рад помочь с понедельника по пятницу, 08:00-18:00 GMT

  • All members
  • Posts: 92
Re: Trigger conditions not met consistently
« Reply #6 on: 26 Jun 2022, 13:30 »
Still no joy I'm afraid.

I'll post the whole trigger here to see if anyone can spot my deliberate mistake...  :-[

It appears to work when it feels like it, and not others. I realise there are issues if any bet goes below 1 penny, but it frequently fails when that isn't the case.

  • All members
  • Posts: 92
Re: Trigger conditions not met consistently
« Reply #7 on: 30 Jun 2022, 10:26 »
In typical computing style :o I have to report that it seems to have been behaving itself for the last few days, and doing what is expected.
Fingers crossed it will continue to do so!

  • All members
  • Posts: 92
Re: Trigger conditions not met consistently
« Reply #8 on: 30 Jun 2022, 19:02 »
...and again in typical fashion, I spoke too soon! Quite a few of this evening's races have no selections when they should have had...

 

Please note, BetFair is seems to be currently OFFLINE