Pages:
Actions
  • #1 by bonecrusher on 06 Feb 2019
  • Hi Guys,

    Is there a trigger/expression that can handle a matched bet on a race which then becomes cancelled before the start of the race due to rain or bad weather.

    As i run a staking plan my trigger looks to the previous triggered event ? My Trigger then gets stuck :(

    My staking plan runs off the info from the statement. And must run in the right order with no duplicate bets as this could lead to serious losses.


    Is there a way to move the trigger on as it does not have a result from the last triggered event which has been cancelled?

    Any help would be great, thanks

    -------

    The problem is not quite the same as a bet not settling fast enough as this can happen also and that stops all betting also.

    Is there a tried a true trigger with expressions that cures these 2 problems ???

    ------

    I like Oxa's fix for the second part of this problem, you can see it here:

    https://marketfeeder.co.uk/learn/triggers/lay-greyhound-loss-recovery/

    at the bottom of that page.

    A complete solution would be great especially for the guys who run their triggers on Market feeder pro VPS.

    Any help would be great, thanks

    bonecrusher

  • #2 by rubold on 06 Feb 2019
  • In Market's race status there are the options of Abandoned & Meeting Abandoned plus the equivalent variables.  Never used these so not certain they will work.
  • #3 by Oxa (WellDoneSoft) on 07 Feb 2019
  • Hello!

    You mentioned my solution for the trigger set that lay in Greyhound.

    This solution can also be applied to any type of markets really. I also come across abandoned races quite often, so this solution has never failed me.
  • #4 by bonecrusher on 20 Feb 2019
  • Quote from: Oxa (WellDoneSoft) on 07 Feb 2019, 13:55
    Hello! You mentioned my solution for the trigger set that lay in Greyhound. This solution can also be applied to any type of markets really. I also come across abandoned races quite often, so this solution has never failed me.

    Helo Oxa,

    Would you able to put up here an example of your solution here that will work with any trigger.

    I have been trying to get it to work with a simple trigger of mine and there is something i am not understanding. Please help :)

    Thanks bonecrusher
  • #5 by Oxa (WellDoneSoft) on 12 Mar 2019
  • The most basic solution is to add this condition next to "Previous Triggered Event's Status is Settled":

    or Previous Triggered Event's Minutes Before the Beginning is less than -15

    This checks if it's been 15 minutes or more since the scheduled start of the previous event, in which case the trigger will ignore the fact that it has not been settled yet.
Pages:
Actions