Bug in 1950 Census Header Review App "unable to save changes".
Tried 3 different states and several pages, however, EVERY time I tried to save I get an error message as shown below...
Refreshing solves nothing...
Comments
-
Same. I did them earlier today (Nevada) with no problem. But tonight (Utah and Arizona) I have the same issue.
0 -
Same, tried a few headers in Oregon and am getting the same messages
0 -
Ditto in NJ
Discouraging. 😒
0 -
Ditto Michigan. 7/5/22
0 -
In Montana if I enter a street name I get "Unable to Save Changes". If I leave the street name blank, I am able to continue the review. I am stopping for now.
0 -
This seems to be some sort of glitch today, but I found a way to work around it. When the box pops up, hit the "cancel" button. Then enter it again. It went through for me every time on the second try.
0 -
Illinois - cancel works one in 5 times (approx), refresh doesn't help at all-just brings me right back to where I was, exiting and restarting doesn't help.. been adding in comment to skip, but it pops up again in my 'feed'... thinking maybe I need to quit for the day... perhaps server can't handle the load today...
edited to add... working in family review
0 -
Same error yesterday and today. Can't review any families after multiple attempts.
0 -
To all of you in this thread, the engineers are aware of the issue . We have been instructed to please click on "Cancel" in the message and keep reviewing the family. So very sorry for the frustration!
0 -
Very frustrating, I get this message on every page that I try to complete. I will walk away for a few days maybe it will be fixed by then.
0 -
CANCEL does not work, the message keeps repeating
1 -
@JAMES VITALETTI1, I am not sure if I understand what you mean by cancel doesn't work and keeps repeating. Do you mean every record you go to you get the same message? I am getting the message also. So I haven't had any problems in clicking on "Cancel" and then "Next" to continue with the review. Are you not able to click the Next and continue? Hang in there for us and keep reviewing. Thank you.
0 -
Earlier today, 5 Jul 2022, I was receiving "unable to save" after entering the street name and clicking 'Next'. When I clicked 'Cancel' it just looped. I ended up pressing the left arrow near the top of the document frame.
0 -
I'm in the same situation as James Vitaletti1. Hitting cancel doesn't work to let me keep working. It just loops and back to the street and I can not get passed the error.
I'm just stopping because as a computer programmer I don't trust that the data is getting saved accurately. I'll try again in a few days.
0 -
I too have been having the same issue, esp. looping when adding a street name. But I just found a workaround. When adding the street name, it creates a button with no words. When the error message comes up, press Cancel, click the blank button, type in the new street name. It will accept it - you may get the error message again, if so, click Cancel and you will be able to continue. Hopefully, they'll get this latest glitch fixed soon.
0 -
The error no longer appears for street name entry, but is still present when trying to save surnames and given names on a multi-page family group. The Cancel button does not work. The error reappears with each click of the Next Part button.
0 -
I feel the same way. I too am a programmer and have found that powering through an error never ends well. I am surprised that the FS engineers are recommending ignoring the error and continuing. I have done a handful simply because the surnames were a mess on the page, and even though I have processed the page before I feel compelled to correct them again in hopes that someone will be able to find the records. I can't see how these records ever passed name review.
0 -
To all in this thread the Unable to Save Changes has been resolved. I have had no trouble at all this morning while testing the waters. If any of you run into any further issues concerning this, please report it and also reach out again in Community 1950 Census so we can get it resolved.
Thank you all so much.
0
