Lotus Bugfest: Updating Authority records via Data import causes errors

Precondition: The .mrc file must include MARC authority record(s) that already exist in bugfest environment. The .mrc file may include records that do not exist and data import will create authority records that do not match IF you use the job profile described in the below steps. Make sure .mrc file contains 010 $a for matches.

1. Go to Data import app. Choose .mrc file that contains MARC authority records to be updated in FOLIO upon import Expected result: Goes to Job Profiles page
2. Select the job profile: Update MARC authority records - 010 $a OR create your own job profile to update MARC authority records Expected result: Default - Update MARC authority records - 010 $a detail record displays in third pane
3. Under detail record Actions menu > Select Run > Are you sure you want to run this job? modal displays and hit Run button on modal Expected result: Return to Logs page
4. Wait for import to complete. Once import is complete then new row will display on Logs profile
5. Go to MARC authority app. Search for any of the records you just updated via data import. Expected result: Any record you updated via data import should be available
6. On results list, click on a record you updated with import Expected result: View source should show that the MARC authority record was updated

Expected outcome: Successful import all records are updated 

Actual outcome: Job returns Completed with errors - See these jobs but it seems all the records are updated 

https://bugfest-lotus.int.aws.folio.org/data-import/job-summary/165dcc67-ad0f-4e1c-8989-0047084be417?sort=recordNumber

https://bugfest-lotus.int.aws.folio.org/data-import/job-summary/6e2ac0b3-30c8-4bd9-8ec5-1bd8b011e047?sort=recordNumber 

This job states records were discarded because of multiple matches. 

https://bugfest-lotus.int.aws.folio.org/data-import/job-summary/d26eef68-fceb-420d-89fb-c3a1e7b49a30?sort=recordNumber