Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2615

Ability to kill a long-running or errored data import

    XMLWordPrintable

Details

    • UXPROD features
    • Folijet
    • 101
    • R1
    • R1
    • R1
    • R1
    • R1
    • R3
    • R2
    • R1
    • R1
    • R2

    Description

      When a data import is taking too long (and may have died without an indication), user should have the ability to manually stop that data import job.

      TBD: when a job is stopped, what should happen?

      • Retain as much as had created/updated properly, and add to log as Completed with errors?
      • Roll back everything that may have created/updated, and add to log as Failed?
      • Any indication needed that a user stopped the job (and if so, who)?
      • What else?

      Question - what about existing jobs that are stuck (see EBSCO demo account for examples). Can they be retroactively updated so that they can be stopped?

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                abreaux Ann-Marie Breaux
                abreaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases