Cymatic Trader Community

Is there an issue with the NEXT command in the circumstance below?
If a race is delayed well beyond the time of the next race, in the autoplay list, which has already finished and is closed itself.
When I then enter NEXT asking for the next race (which is already closed), after the delayed race completes, excel reports the closed race as being the next race. But nothing more.
Then when I try to enter NEXT again to try shuffle along to the next race in the autoplay list, Cymatic doesnt seem to react.
This means my logic becomes stuck.
I have only noticed this in Australian Horse racing, so far, where the races can be closely packed, time wise.

Hi FrenchHorn,

I seem to recall that the autopilot assumes that the presence a closed race means that racing for the day has finished and thus doesn't try to move forward any more. I think it had to be done like that to prevent an infinite loop constantly trying to move forward. It might be that this logic is affecting the ability to use the NEXT command when there is a closed race in the mix.

I think that a search of the forum might reveal previous discussions bout this topic (I recall discussing it before), that may have explained ways to work around the problem for the autopilot and perhaps thus for the NEXT command too.

Kind regards,

Gavin