Issue description

When users run the CCMA pre-migration checks, they can sometimes run into a non-descriptive error for the Users and groups checks, "We found an unexpected error and couldn't complete the check."

Example message

For example, under "We couldn't check the user limit of your cloud plan" or "We couldn't check for invalid users" checks we see the following error message.

We found an unexpected error and couldn't complete the check. We won't be able to run the migration, and you'll need to check for the errors manually. Refresh the checks to try again.

Contact support if you continue to get this message.

Logs

The following errors might be thrown in the application log.

2024-07-02 09:58:18,032 ERROR [Caesium-1-2] [service.check.email.InvalidEmailChecker] error An error occurred when checking for invalid emails for cloudId: <cloud id>
 -- checkExecutionId: f5c904606a581336b7325a6ef219b9a80dab1234
java.lang.RuntimeException: com.atlassian.migration.agent.okhttp.HttpServiceException: Bad request. Status code: 401, message: , headers: date: Tue, 02 Jul 2024 07:58:18 GMT

Workaround

This error can be due to a number of reasons. First make sure the user has the proper permissions to run the migration and that there are not any invalid emails in the server.

• 3. Ensure you have the right permissions [mandatory]
• Invalid email addresses
• Renew Token in Confluence Cloud Migration Assistant(CCMA)

If this doesn't solve the problem, please reach out to support.