Issues with Record Availability in the App
I enjoy indexing and frequently use the app (almost daily). I used to be able to get through 50 names fairly quickly as there were always records available. However, ever since the app was updated, it has been so slow, and in one short session of trying to get names completed, I frequently get the error message "Records for this country are temporarily unavailable. Please try again later." This will happen over and over again. In the time I used to review 50 names, I maybe get 3 done. Is this a common issue? Or is it just me? I don't put any additional filters on, I just leave the country on the United States, any state, and no specific last name. I would think there would be records constantly available, but this has not been the case recently.
Answers
-
I know AWS had major internet connectivity issues on Monday and Tuesday and maybe it was this that was causing your issues. I just tried the Quick Name review and had no issues at all. I also used the Full name review to check and did not find any issues with speed or in obtaining names. If you havent done so recently you may also want to clear your cookies and cache from your system in order to speed up your computer. To do this you can go to FamilySearch reset your Cookies. Or you can clear them on your browser. For Google browser you go to the 3 vertical dots in the upper right corner of the page
go to Delete browsing data
For a MS Edge browser you you go to the 3 vertical dots in the upper right , click the dots and go to delete browsing data.
Hopefully your problem is already fixed but if it continues feel free to respond with more information and screen shots of your issue.
1 -
Thank you for the reply. This actually isn’t in the browser, it’s on the mobile app. I’ve attached a screenshot of the error message I frequently get.
0 -
Apparently the error message picture was against the guidelines and got rejected. I will try again.
0 -
The image loader was really slow yesterday for unknown reasons, but I see your image is posted now. I have the exact same error message. I will send this up for review and see what can be done.
0
