Hi, I have recently started the Data Migration task in Super admin console. After starting the job, I have received a notification saying "Running data migration" and after a while when I came back to the admin console tab, there was no acknowledgement regarding the data migration. In the Cloud Watch logs, I can see "Reindex completed" log for different resources. I am confused whether my data migration is completed or failed. When I visit "https://app-staging.neelyx.bio/admin/super/asyncjob", I can see the message "Failed to load migration info". Is there a way to check if my data migration is successful or failed. Thanks

hey @rk00600 , can you query your AsyncJob resources by doing something like

GET https://app-staging.neelyx.bio/fhir/R4/AsyncJob?type=data-migration

Hi @finnbergquist, The command you shared is not working. I am getting Error not found. I used the following command

medplum post admin/super/setdataversion "{ \"dataVersion\": 1 }"

The output is

{
  "resourceType": "OperationOutcome",
  "id": "ok",
  "issue": [
    {
      "severity": "information",
      "code": "informational",
      "details": {
        "text": "All OK"
      }
    }
  ],
  "extension": [
    {
      "url": "https://medplum.com/fhir/StructureDefinition/tracing",
      "extension": [
        {
          "url": "requestId",
          "valueId": "b5f9c06f-1229-4448-bccf-1275cd9841fc"
        },
        {
          "url": "traceId",
          "valueId": "1-68a5d382-25f3ee2f44d763e76c49bea5"
        }
      ]
    }
  ]
}

Ahh gotcha, that request would actually need to be

<your-server-url>/fhir/R4/AsyncJob?type=data-migration

not your app URL

Hi @finnbergquist I just upgraded my medplum prod server from 3.2.12 to 3.3, but I don't see the "Run Data Migrations" button in my admin console.

You may need to upgrade medplum app to the matching version of medplum server to see the button. You can see the current version of medplum app by inspecting the html within the

<head>

or running

document.querySelector('[name="medplum-version"]').content

in the console.

Thanks @nathan-watkins-unityai My medplum app version is same as the medpum server version. Is there any other way to run the data migration or is there a way to validate the status of the data migration?

Hi @rk00600 - the 3.3.0->4.0.0 upgrade was admittedly a rough one. We wrote up a longer form guie at the time: https://www.medplum.com/blog/v4-upgrade See the section on "Skipping the Migration (For Deployments Started on 2.2.0 or Later)", which applies to most people. That's the fastest way to get through it.

Thanks a lot @cody I skipped the data migrations by setting "dataVersion" to 1 and upgraded the server to 4.0 version. Everything went smooth during the process. After that, I have upgraded to 4.1.0 and all the post-deploy migrations are completed. But when I deployed 4.1.12, I am facing issues with the post-deploy migrations. One of the AsyncJob is in accepted status forever, the job doesn't have Parameters in the output. This job is preventing the following jobs to execute.

how long is "forever"? how much data is in your database?

Thanks a lot @cody for your quick response. There isn't a lot of data. For reference, post-deploy migrations after 4.1.0 took around 35 minutes. But, new AsyncJob is still in accepted status since 6 hours. Also, AsyncJob resource doesn't have any Parameters in the output and I haven't seen any logs in my AWS ECS Task.

Was there any notable output in the server logs (i.e., in CloudWatch Logs)?

There is no notable output in the server logs, all the logs are operations related(creating resources, email and authentication). The AsyncJob is still in accepted state. Does that mean the job has failed? Is there a way to check the current status of the job?

@rk00600 , I wanted to follow up with this one here. Did you get this resolved?

Thanks @Ian Plunkett , the issue is now resolved. The Asycjob stayed in accepted stage for almost a week and when we tried again, It executed.

Just curious- what prompted it to "try again"? Redeploying?

My teammate clicked the Run data migration button and the Async job is completed. We really don't have an idea why it happened