We couldn't check for users/agent count limit
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
The following documentation provides guidance on resolving the error messages below:
- We couldn't check for users count limit
- We couldn't check for Jira Service Management availability in cloud
- We couldn't check for agents count limit"
Overview
When using the Jira Cloud Migration Assistant or Confluence Cloud Migration Assistant, if the pre-flight check encounters an issue with "We couldn't check for user count limit", a grey icon is displayed. Or, if the migration plan is for Jira Service Management, warning messages may also appear for "We couldn't check for Jira Service Management availability in cloud" or "We couldn't check for agents count limit" like in the below screenshot
And, in the application logs, the below error can be seen:
2022-02-05 22:13:22,189+0000 pool-113818-thread-226 WARN hjennings 1333x23619353x1 yyyyyyy xx.xxx.xx.xxx,xxx.16.1.4
/rest/migration/latest/check/0a5adxxxxxxxxxxxxxxxxxxxxxc7bbe33dc3ef [c.a.j.migration.preflight.PreflightService] check execution 0a5adcea18b38b7685d5e3552770c7bbe33dc3ef failed
java.util.concurrent.ExecutionException: com.atlassian.jira.migration.httpclient.exceptions.UnexpectedStatusCodeException: Received an unexpected status code; expected [200], but received 401: {"code":401,"message":"Unauthorized"}
at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1067)
at com.atlassian.jira.migration.preflight.ProjectConflictService.performProjectKeyNameConflictCheck(ProjectConflictService.kt:85)
at com.atlassian.jira.migration.preflight.ProjectConflictService.performCheck(ProjectConflictService.kt:72)
at com.atlassian.jira.migration.preflight.ProjectKeyAndNameConflictCheck.performCheck(ProjectKeyAndNameConflictCheck.kt:28)
at com.atlassian.jira.migration.preflight.AsyncCheckExecutor.runCheck(AsyncCheckExecutor.kt:182)
at com.atlassian.jira.migration.preflight.AsyncCheckExecutor.executeChecksListenable$lambda-14$lambda-12$lambda-10(AsyncCheckExecutor.kt:105)
at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:125)
at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57)
at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.atlassian.jira.migration.httpclient.exceptions.UnexpectedStatusCodeException: Received an unexpected status code; expected [200], but received 401: {"code":401,"message":"Unauthorized"}
at com.atlassian.jira.migration.httpclient.exceptions.ExceptionsKt.unexpectedStatusCode(Exceptions.kt:7)
at com.atlassian.jira.migration.httpclient.AbstractPluginHttpClient.checkExpectedResponseCode(AbstractPluginHttpClient.kt:134)This issue may arise when the migration process spans an extended period, such as weeks, and there is a gap between migration plans.
Root Cause
Due to the extended migration gaps between the migration plan, the authentication token utilized by the Jira/Confluence Cloud Migration Assistant to establish a connection with Atlassian cloud servers expired, resulting in this issue.
Solution
Renew the CMA authentication token in order to resolve this issue.