Change Details

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 we are just communicating that the saving failed. If the user continues editing (or presses "crtl+s"), another attempt to saving will happen. However users may not try again to save because they completed their work or interpreted the saving error as an unrecoverable error. # Proposed solution Once a saving fails we can make a new attempt automatically. Present the error as "Unable to save. Retrying in in a moment..." and try saving again after a few seconds. For metric purposes, we should avoid the re-attempt strategy to generate artificial noise in our metrics. So we may want to avoid counting each re-attempt as a separate errors.

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.

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 we are just communicating that the saving failed. If the user continues editing (or presses "crtl+s"), another attempt to saving will happen.However, However users may not try again to save because they completed their work or interpreted the saving error as an unrecoverable errordue 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 Once a saving fails we can make a new attempt automaticallyWe can communicate more clearly that saving will be attempted again. PThe proposal is to present the error as "Unable to save. Retrying in in a moment..." and try saving again after a few seconds. For metric purposes, we should avoid the re-attempt strategy to generate artificial noise in our metrics. So we may want to avoid counting each re-attempt as a separate errors.to make the user aware that saving will happen again after a few seconds.