Rich Feedback in Error Messages
N
Novel Toucan
Issue: While creating branching script, it is easy to make mistakes. In a recent attempt to create a script I received an error message because I enabled branching in two separate questions while simultaneously marking that the section should continue to a specific section. This was an error where I should have disabled branching and utilized the "continue to specific section" feature only.
After multiple-save attempts, I kept seeing an error message. There was no indication that progress was saved, nor was there information about what the error was. When I reloaded my page - a risky choice since reloading without saving in script building is a destructive action - my script showed duplicates of the questions with the errors. The script duplicated "GOTV Ask" enough to take my 12 section script to a 26 section script.
These issues are related. Without rich error messages, it is difficult to find the problem. When the error message appears during saving, the problem area is duplicated, but this is only visible when the page is reloaded. Reloading without saving is a potentially destructive action, erasing user progress.
Potential Solution(s): 1) Error messages should give the user more information about what the issue is and where to find the error. It should - if possible - also offer a fix. 2) Script building should save progress automatically or encourage saving the script before reloading to avoid destroying progress 3) Errors during saves should not duplicate the area of the script throwing the error.