"A job instance already exists" error bulk editing Items on large bulk edit job

Overview:
Log into https://bugfest-mg.int.aws.folio.org/ or https://bulk-edit-perf.ci.folio.org/ as a User with  "Bulk Edit: In app – View", "Bulk Edit: In app – Edit" permissions. 
*User uploads a .csv file with a large amount (10.000) "Item barcodes" and starts Bulk edit.
**Bulk edit done, successful notification is presented, but  no changes  applied. 
***The Preview of records changed shows records without  changes
{}*{}{}*UI side doesn't present any report{*} that Items were not updated.
****{}{}BE side reports the issue: *ERROR BulkEditController   A job instance already exists and is complete for parameters
The issue reproduced time to time with large data set

Steps to Reproduce:

1. Navigate to the Bulk edit app => Select Inventory-Items App => Select " Item barcode" from "Records identifier" dropdown
2. Upload a .csv file  with "Item barcodes" Items_barcodes_10.000_MG.csv by dragging it on the Drag & drop area
3. Click "Actions" menu => Select "Start bulk edit"
4. Modify the Items  =>Click  "Confirm changes"
5. Click "Commit changes" on the "Are you sure" form
6. Check the Bulk Edit page  with confirmation banner
7. Check the Preview of records changed
8. Make sure that Items were updated

Expected Results:
 6. The confirmation banner shows correct numbers of records changed

7. The Preview of records changed shows Items with applied changes

8. The Items are updated

Actual Results:

The Bulk edit is failed, but no notification is presented

The Preview of records changed shows a part of Items without applied changes/
The Items were not updated
Additional Information:
URL: https://bugfest-mg.int.aws.folio.org/ or https://bulk-edit-perf.ci.folio.org/

The "Export manager" shows job with status "Successful"
Logs:
MG Bugfest env id=47f7b087-17f0-4cf0-b468-a1450f589ad4:
id=47f7b087-17f0-4cf0-b468-a1450f589ad4.txt
Bulk edit env:
worker_error_job_already_exists.txt

One of the possible reason is having the same job for both of BULK_EDIT_IDENTIFIERS and BULK_EDIT_UPDATE job types, and when running multiple jobs, from time to time it happens that it tries to start the job that has already been completed.

Interested parties: