Can you upgrade to version 4.2.1 and try again? We have verified on this version and the issue is not reproduced.