Hi Mark,
Thanks for the post.
Andy is correct. We had an issue were users were getting this error on specific occasions. Upgrading to the latest version should address this issue. Please try the same and do contact us if you need any further assistance.