You saved it. This is it. Upgraded to the latest (aba08d1929) and the problem is solved. But the latest release (2.8.0.beta6) didn’t fix the issue.
Wondering why this issue did not crop up on other discourse instances that we are running which are all at 2.8.0.beta6.