Forum Discussion
Matthias
3 years agoNew Contributor III
There was a new patch release (4.31 Patch 3) - which we installed as soon as it was available (support notified us about it, and that it should include a fix) - which fixed the issue.
We haven’t had this problem since (we updated to that version late december).