We thought we had this problem with v5.3 and were advised to updated to rev2 as there was a specific fix for this problem in that patch release.
As it happened we didn’t have this problem but hopefully this may help as it is specifically mentioned in the release notes for 5.3 rev2.
Regards
Garry
