Hotlinks for created/updated records not displayed in the log

Overview: Sometimes the created/updated labels in the Data Import log do not display as hotlinks, like they should. I happened to encounter this today, and one cause may be new Kafka topics have to be created for the import actions, which takes extra time, and if the log is displayed too quickly, the created/updated term and the hotlink for that term may not display.

Current workaround: Go to the Inventory or other app and search for the record directly

Steps to Reproduce:

1. Log into FOLIO-snapshot or Snapshot-2 as diku_admin
2. Go to Data import
3. Check all the logs for the day to see if any jobs have already run that will create orders. If yes, try the other environment, or wait until the Snapshot or Snapshot-2 environment refreshes.
4. Go to Settings/Data import/Field mapping profiles and create the following
   • Field mapping 1:
     • Name: Open order for Physical resource with Inventory test
     • Incoming record type: MARC Bib
     • FOLIO record type: Orders
     • Purchase order status: "Open"
     • Approved: checked
     • Vendor: look up GOBI and assign
     • Title: 245$a
     • Acquisition method: Select from the dropdown list
     • Order format: Select "Physical resource" from the dropdown list
     • Receiving workflow: Select "Synchronized" from the dropdown list
     • Physical unit price: "20"
     • Quantity physical: "1"
     • Currency: "USD"
     • Location: Select a value from the dropdown list
     • Location quantity physical: "1"
     • Location quantity electronic: [blank]
     • Physical resource accordion/Material type: Select "text" from the dropdown list
     • See profile https://bugfest-orchid.int.aws.folio.org/settings/data-import/mapping-profiles/view/c654fe93-b70a-4647-bb2e-63e92d9baba5?query=open%20order&sort=name on Orchid Bugfest
   • Field mapping 2
     • Title: Open orders - create simple holdings
     • Incoming record type: MARC Bib
     • FOLIO record type: Holdings
     • Permanent location: Select a value from the dropdown list
     • See profile https://bugfest-orchid.int.aws.folio.org/settings/data-import/mapping-profiles/view/5ed6df36-85f4-43f0-b239-e212fa5ca177?query=open%20order&sort=name on Orchid Bugfest
   • Field mapping 3:
     • Title: Open orders - create simple item
     • Incoming record type: MARC Bib
     • FOLIO record type: Item
     • Material type: select a value from the dropdown list
     • Permanent loan type: select "Can circulate" from the dropdown list
     • Status: select "On order" from the dropdown list
     • See profile https://bugfest-orchid.int.aws.folio.org/settings/data-import/mapping-profiles/view/ae0afe3b-c7cd-4534-bb5b-25b972220079?query=open%20order&sort=name on Orchid Bugfest
5. Go to Settings/Data import/Action profiles
6. Create action profiles and link to the 3 above field mapping profiles
7. Go to Settings/Data import/Job profiles and create the following
   • Name: Open order for Physical resource with Instance, Holdings, Item
   • Accepted data type: MARC
   • Add Create order action from above
   • Add Default - create instance
   • Add Create holdings action from above
   • Add Create item action from above
   • See profile https://bugfest-orchid.int.aws.folio.org/settings/data-import/job-profiles/view/b4d0b5e2-1c1a-490f-8932-00e4db1d2072?query=open%20order&sort=name on Orchid Bugfest
8. Go to Data import
9. Upload the attached MARC file and assign the newly-created job profile
10. As soon as the job finishes, click the file name hotlink at the top of the log list
11. Check for "Created" term in SRS MARC, Instance, Holdings, Item, and Order
12. Check for hotlinks on the "Created" term in Instance, Holdings, Item, and Order

Expected Results: User should see "Created" for SRS MARC, Instances, Holdings, Items, Orders, and each (except SRS MARC) should be a hotlink

Actual Results: Originally, the "Created" term was not showing for Holdings and Items. After a refresh, the terms showed, but they never became hotlinks

Additional Information: See attached videos. It shows really clearly on Snapshot 2, and not quite as clearly on Snapshot - but it definitely reproduced on both envs