We’ve managed to reproduce the issue on an internal test server and have a possible lead on the underlying cause of the issue. We do not have an ETA on a full-fledged solution yet, but the investigation continues and appears to be bearing fruit, which is good. Thanks for your patience!