Page MenuHomePhabricator

CX2: Communicate that auto-save is retrying automatically after an error
Open, MediumPublic

Description

Auto-save allows users to keep working without having to think of saving their progress all the time. However, due to network issues a possible attempt to save may fail.

Currently, when an error occurs, saving is attempted again after a few seconds (which is good), but we are just communicating that the saving failed.

Proposed solution

We can communicate more clearly that saving will be attempted again. The proposal is to present the error as "Unable to save. Retrying in in a moment..." to make the user aware that saving will happen again after a few seconds.

Event Timeline

Pginer-WMF raised the priority of this task from to Needs Triage.
Pginer-WMF updated the task description. (Show Details)
Pginer-WMF added a project: ContentTranslation.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 23 2015, 2:56 PM
Amire80 renamed this task from Make auto-save errors less critical by retying automatically to Make auto-save errors less critical by retrying automatically.Jul 23 2015, 5:19 PM
Amire80 triaged this task as Medium priority.
Amire80 set Security to None.
Amire80 moved this task from Needs Triage to CX6 on the ContentTranslation board.Jul 28 2015, 6:29 PM
Amire80 moved this task from CX6 to CX7 on the ContentTranslation board.Oct 1 2015, 8:37 PM
Amire80 moved this task from CX7 to CX8 on the ContentTranslation board.Jan 24 2016, 10:30 PM
Pginer-WMF updated the task description. (Show Details)Feb 25 2016, 1:36 PM
Amire80 moved this task from CX8 to Bugs on the ContentTranslation board.Apr 20 2016, 1:12 PM
Arrbee moved this task from Bugs to Check & Move on the ContentTranslation board.Nov 26 2018, 1:49 PM
Etonkovidova moved this task from Check & Move to Enhancements on the ContentTranslation board.EditedDec 1 2018, 1:18 AM
Etonkovidova added subscribers: Pginer-WMF, Etonkovidova.

The issue ( to improve communication of intermittent not-saved translation error) is still present.

@Pginer-WMF's suggestion
> present the error as "Unable to save. Retrying in in a moment..." and try saving again after a few seconds"
will improve such communication.

Presently, if the message "An error occurred while saving the page" is displayed to a user due to e.g. a network interruption, and then the network connection restored, it will take a normal cycle of saving (about 30 sec) to display 'Saved just now'. All those 30 sec "An error occurred ..." is displayed to a user wrongly indicating that the problem persists.

Pginer-WMF renamed this task from Make auto-save errors less critical by retrying automatically to CX2: Communicate that auto-save is retrying automatically after an error.Dec 5 2018, 9:51 AM
Pginer-WMF removed a project: WorkType-Maintenance.
Pginer-WMF updated the task description. (Show Details)

Thanks for testing this, @Etonkovidova.
From your comment it seems that the current behaviour supports half of this ticket (saving is retried automatically) while the other half is pending (communicating it). I've updated the ticket description to focus on the pending part.