-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle failure of copy tasks #2850
Comments
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. |
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). |
@bjester sir to offload some of your load for the next major release, maybe I can take this one? |
@vkWeb Yes you can take this on, as I haven't done any work towards it. @AllanOXDi had mentioned interest in working with me on it. Perhaps you can followup with him on it? |
@bjester Sure sir, I'll talk to Allan about this and I will start working on this after getting change event PR merged! |
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/
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
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.
The text was updated successfully, but these errors were encountered: