Hi @jthomas - here is the Jira issue for that particular issue - DHIS2-14917. It has been fixed in the 2.38.3 release. As you’ve noticed, setting system.program_rule.server_execution = off is a workaround for affected versions including 184.108.40.206
Please let us know if upgrading to 2.38.3 solves your issue!
I just deployed 2.38.3 to one of our production servers. One earlier issue is resolved, but the patient listing of the tracker is now reversed; the old record is showing at the top and creating serious inconvenience. Please look at the issue immediately. Should be more careful on testing before release,