So, working with support, the fix for this was to upgrade to version 4.0.3 and restore the database from backup.

Thank you.