Hello!
Just to let you know that I am still working to reproduce this bug (did not succeed yet, but I keep trying), and the program log you sent the other day (along with the detailed explanations) helped a lot.
What I can suggest as a temporary workaround is to limit the trigger to back only on X selections at a time.
So in the conditions, add the following condition to the end of the list:
and Selection's Trigger Expression match_index is equal or less than XThis way, even if it goes crazy and activates 10 horses, it will only back on the first X of them, which should limit your losses.
Only active races were affected this time
By active, do you mean the race was refreshing?