Attempting a large external import where the import is aborted by the system fails to resume after underlying issue is fixed

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • Component/s: Assets - Import
    • None
    • 4
    • Major
    • 0

      Issue Summary

      This is reproducible on Data Center: no

      When attempting a large external import, the import might get aborted by the system due to certain unexpected problems. If the underlying cause is fixed, the import should resume (as it does for other types of imports such as CSV or JSON imports). However, for an external import, this process does not automatically resume. 

      Steps to Reproduce

      This can't be reproduced always as this occurs when an import is aborted unexpectedly. 

      1. Follow steps 1-5 in this guide for external imports with a large amount of data

      Expected Results

      In the event that the import is unexpectedly aborted by the system and the underlying cause is subsequently addressed and a re-start is triggered, the import should resume automatically. 

      Actual Results

      In the event that the import is unexpectedly aborted by the system and the underlying cause is subsequently addressed and a re-start is triggered, the external import does not resume automatically. 

      Workaround

      The only workaround would be to carry out the external import again from scratch after confirmation from the support team that the underlying issue is fixed.

            Assignee:
            Dorothea Linneweber
            Reporter:
            Kalanika Weerasinghe
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: