Family Review dies
For three straight days, I've tried to use Family Review. Once it was for Uruguay, once it was for Argentina, once it was for Paraguay, once it was for Chile. Every time, the app died with a message that "An unknown error occurred. Wait a few minutes and try again". It never came back.
Could someone tell the FR engineers?
Answers
-
@Jerry Hill and @Ashlee C. this problem landed in the indexing community - please redirect Thanks 😎
0 -
Well, it is an indexing problem.
And for another two consecutive days, I am unable to complete a record in Family Review without the "Some error occurred" message. This was true for four different countries, so it's the program not the data.
0 -
@Ashlee C. can you confirm that engineers are aware of this issue please.
0 -
@Jerry Hill I will send this in to be looked into. Thank you for bringing it to our attention and for your patience while we work towards a resolution.
2 -
Thanks.
With all the Spanish projects gone from Indexing, and the Family Review app so unstable, I am unable to do anything.
0 -
Add this to what you tell the Family Review engineers:
I check each day to see if any progress has been in the data or app. Most of the datasets have been very poorly transcribed by your vaunted AI. I am actually quite thrilled when it gets some of the fields right. It obviously hasn't been coached well on beginning Spanish because it makes a lot a basic errors, even on printed forms. On some of the more hammered handwritten images, it sometimes gets nothing right. This means the reviewer (me) has to spend an awful lot of time finding or correcting the data, and making the correct highlights. And then all that time is wasted when, after hitting 'Save', I get the "Something went wrong Try again" message.
I just wasted 15 minutes on an Uruguay image. When it first came up, I suspected trouble — the message was "<Unknown> is the principal of this record". I looked at the image and told it No. It wanted me to select the principal from the list — it wasn't on there. I then proceeded to add the name and highlight it on the image. After hitting 'Save', it did not save anything. I went back and repeated the add and highlight routine — 3 times — and it wouldn't save. I just quit and bailed out.
I am really reluctant to recommend this to any Spanish speaking friends.
0 -
Two more days. Four more countries / batches abandoned with "Something happened. Try again later".
@Ashlee C. Do the engineers know that it always dies on a 'Save' ?
0 -
Thank you for researching this further. I will let the engineers know. We appreciate your patience.
0 -
@Jerry Hill thanks for submitting your issues. I've been doing Family Review for the last 6 months and have completed over 700 records. There are issues with the tool, but I have carefully documented each issue and applicable fixes, and recorded several video sessions. I am planning to share my video with the community through a webinar presentation. I'm trying to recruit Spanish speakers to join us in this important work.
I have encountered all of the issues you mentioned. But the latest one is a show stopper. This started happening in the last few weeks. "An unknown error occurred. Wait a few minutes and try again" You can't recover from it and have to abandon the record or submit it with errors.
This issue happens when you correct highlights. Once I discovered this, I could easily reproduce it every time. For instance, if the parts of a name are not highlighted correctly, if the system left out an initial or the name is broken between two lines. The system only highlights one or more parts, but not the full name. When you try to correct these errors, the highlighting edits are not saved and you get the "unknown error" message.
@Ashlee C. There are a ton of highlighting issues in these records. I had to abandon 5 batches yesterday, and I wasn't able to submit any of my work. I'm taking a break until I hear that the problem has been fixed. Please keep us posted. Thanks.
1 -
I would love to be doing it, now that Spanish Indexing has died. However, I can't get past the "Unknown Error message. I keep trying a batch or two each day to see if they've fixed it. 10 days; 20 batches later — still no joy.
All I know is that it dies on Save. Based on what you say, I suppose we could get by if we didn't change any highlights. But sometimes those highlights are so screwed up . . . . . But that is ignoring the need to get the program working properly.
Meanwhile, I can't do anything (and I assume nobody else can) cuz the program is faulty. AI is not what it's cracked up to be.
Your videos may be useful cuz they give practically no hints as to how it's supposed to work — just vague generalities that are obvious to a casual observer.
0 -
I hope they get something fixed soon. I was an administrator of the Spanish Completion Team. We had over a hundred experienced Reviewers there who now have to find something else to do with their skills. I would like to tell the all to jump over to Family Review, but I'm not going to do so as long as it is this unstable and unusable. I am fearful we'll lose some if we can't give them a new task.
0 -
Still dying with the same error.
0 -
@Ashlee C. now that I'm trying to work in the Opportunities, I really don't believe that all the United States families have gone thru Family Review and been done correctly. Furthermore, when trying to fix Vitals and other family history errors for all the names in the Archives doesnt work either when FS allows people to make changes without getting proper and accurate Sources/documentation so where do I take this problem?
0 -
I am a former member of the Spanish Indexing Completion team, and there is another way I can help out. Perhaps you can contact me directly outside of this thread. My contact information is any of the handouts attached to past FamilySearch webinars that I presented. You can search for my name here: https://www.familysearch.org/en/wiki/Panama_Online_Learning
I am still experiencing problems with "unknown error" regarding highlights, but today I had an improved experience. I was able to successfully edit a few highlights and submit a few records. However, I ran into a problem with a record that was missing the birth date. When I added a new Date field to the Birth and tried to highlight the date, I got the "unknown error" again. It seems that engineers have been working on it, but there are still some issues left. Thanks for your continuing support.
0 -
Any progress on the Family Review dying issue?
I about had a heart attack yesterday because one FR record I had went through OK. I don't know what went wrong but the AI got almost all the names correct and the highlights were spot on. The only thing wrong was that it had the godfather as the primary — but at least the correct primary was in their list and I didn't have to adjust highlights..
Unfortunately, the next record died with the standard error. In that case, the highlights were screwed up and I had to adjust them. Highlights changes were one issue that @A Nelson suspected was causing the "Unknown Error" error.
Oh well. At least I got one record submitted.
0 -
@Jerry Hill The engineers are aware of this issue and working on it. We don't have a time frame for this one, but they are working. Hopefully we'll see something soon.
0 -
I left a big comment for you on the Costa Rica thread. Tell the engineers thanks for getting that fixed.
A different issue that needs a lot of work is the AI program's recognition of names and relationships.
There are way too many record for which it says "<Unknown> is the primary person in the record". This is in spite of the name being very plain and obvious in the image. The only way you can figure out which record it is referring to is by looking down the list of other names in the record, and then reading through the image until you locate some matches. Usually the primary's name is not in the list of names the program has made for the image, so you have to add it and its highlights manually. It's a long and aggravating process.
Similarly, it is ridiculous that the AI can't get relationships right on printed forms. That would be the simplest of tasks for a human but the AI program can't seem to read or interpret basic Spanish correctly. Of course, it could be forgiven for having trouble figuring out relationships in the long, hand-written records. Those are tough for all but experienced Spanish speakers. Back in the old days of human indexing, you could tell the non-speaker indexer because they would just go through the record and grab the first name or date they found. Putting them in the right fields was random — a shot-in-the-dark because they didn't know the relationship terms.
@A Nelson This gets into some of the things we discussed the other day.
1
