Uploaded image for project: 'ui-data-import'
  1. ui-data-import
  2. UIDATIMP-655

Data imports can get stuck at "Running" in the UI when they may actually have completed fully, partially, or not at all

    XMLWordPrintable

    Details

    • Template:
      Folijet UI bug template
    • Sprint:
      Folijet Sprint 99
    • Story Points:
      0
    • Development Team:
      Folijet
    • Release:
      Q3 2020
    • Affected Institution:
      Lehigh, Simmons
    • Epic Link:

      Description

      Overview: Data import batch loads can get reported in the UI as "Running" - appearing to be stuck at a certain percent. When records from the stuck file are checked in Inventory there is a range of possibilities for what is actually occurring: The import could have been successful, all records imported. The import could have been partially completed. Finally, the import may have failed completely. Without this information it is impossible to know how the process has affected the SRS and Inventory.

      Current workaround: Even after running a MARCEdit's MARC validator on the file, the file needs to be imported into a test environment. If the import process stops the only workaround I can think of is to query the ldp test environment when that is updated to see which records were successfully imported or updated and which were not. Even then, you may not be able to determine why an import stopped. I don't think there is a true workaround for this, unfortunately.

      Steps to Reproduce:

      1. Log into FOLIO-snapshot as diku_admin
      2. Click on Data Import
      3. Upload a file of 5,000 or more records using the Data import hidden button. I've only experienced this error with batches of this size, although it could happen with smaller ones. I'm not sure. They just seem to fail and report accurately that they have failed when the batch is smaller. I will give a link to a MARC file (too large to upload here) for testing. This file has been run through MarcEdit's validator.
      4. If the Running report stops, then some error has occurred.

      Expected Results: What should happen. The job should run to completion or fail completely, giving some information as to why the job failed.

      Actual Results: The job appears to be "stuck" and there's no way of telling what has changed in the data stores

      Additional Information: Validated MARC File for testing:
      MARC file - https://drive.google.com/file/d/1JAdpDEIc3uQMtaQHGlk7le7bYWwueXIz/view?usp=sharing

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                abreaux Ann-Marie Breaux
                Reporter:
                lmccoll_lyu Lisa McColl
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases