Handle failure of copy tasks

[metodimilevqa]

Summary

Sometimes a red loader/spinner is seen when the user tries to import from channels - as it is unclear why the loader is red but not green we need to handle this better on the FE and make it more clear for the user what exactly is happening (task failed).

Category

BUG

Usage Details

Experienced at: https://studio.learningequality.org/

• Windows 10
• Browser: Chrome (latest)
• Channel: ziviv-fodon

Screenshots

Real-life consequences (anything community should be aware of, for instance how it affects end users)

Unclear for the user that the task has failed.

Expected behaviour

• "Copy failed" text
• A "Retry" action
• An icon to remove the failed task
• An error icon in the side panel (more specs in image)

This will require some backend work to allow 'retry' of a failed copy task. The simplest way around this would be to delete the previously failed copy and then do the copy again.

In order to ensure the proper order of operations for this, this is best done after some clean up of the sync behaviour.

[rtibbles]

We need to alert to the user that a task has failed, and also do a delete to roll back any copying that has happened so far.

[jtamiace]

Looking for some review on this recommendation, which is to replace the red spinner with the red error icon along with:

• "Copy failed" text
• A "Retry" action
• An icon to remove the failed task
• An error icon in the side panel (more specs in image)

[rtibbles]

This seems like the appropriate change - the main thing from a technical perspective will be to either allow resuming the current copying job, or deleting the first attempted copy, and then retrying (the latter strategy is less efficient but seems more sure fire).