This message was deleted.

All I can say is that we encountered the issue described in the link with 2.7.2 and upgrading to 2.7.5 did fix it for us. So I’d guess your issue is separate from that one