I wonder if they have some 2nd pass filter that scans the output in a much more straightforward and thus hard to cheat way, and tweaks the main model to prevent "abuse".
I don't think it's that complicated. The output to any input is non deterministic. Some borderline queries will sometimes work other times get rejected.
I sincerely doubt they just nuked this query in 15 mins. Much more likely is that it had a 1 in 4 chance of succeeding originally, and now when you ran it, you hit the 3 in 4 case of rejection. Try running it again or in a new session.
I sincerely doubt they just nuked this query in 15 mins. Much more likely is that it had a 1 in 4 chance of succeeding originally, and now when you ran it, you hit the 3 in 4 case of rejection. Try running it again or in a new session.