“AMR job xxxxxxxxxxxxxxxx is not an active job”
This error may be encountered where the AMR change token can overwhelm the backend database. In such an event, Microsoft will terminate the AMR call. A long-term fix for this issue is not yet available.
As a workaround, we recommend resetting the line items and rerunning the migration pass to trigger a fresh AMR call.