Sorry for the delay Zac, was on leave and just got back. We’re almost there…I upgraded to 3.22 and re-ran the scenario and the bug fix works but only if the ESF query returns 0 rows (my bad for simplifying to a zero vs one record case). The more realistic scenario is if you have two or more followers (ESF query result not zero) and then add/remove a follower. In this case the Follower model does not perform the same “No Value Behaviour = Abort Query” logic and doesn’t refresh it’s condition from the ESF model query result and you get the same issue, does this make sense? Is there some way to “force” the model to re-query AND rebuild the conditions like it does on page load or “abort query” scenario?
