Home› Ask a Question› Search

error loading picture.. please try later

«1234»

Answers

  • deliamarcon1
    deliamarcon1 ✭
    January 4, 2023

    4th of January 2023, after 4 years of waiting for new records to come in no matter what I try images do not load :(

    1
  • Mike357
    Mike357 ✭✭✭✭
    January 5, 2023 edited January 7, 2023

    I can add just one bit of information that may bear on this topic. I understand that a throttle is built into the system, and is used when people are browsing images: if they access images very quickly, the system starts throwing up the "Image not available" error. This may impact some who are having this issue.

    1
  • Dan Mackin
    Dan Mackin ✭
    January 5, 2023

    @Mike357 appreciate you confirming the throttling issue that many in this thread have been very frustrated with. I don't believe that the thread should be shutdown until the problem has been solved. Does family search have any plans to allow a larger number of images to be browsed in a time period? Some of us require many hundreds of images in a day. If nothing else please open a new thread for discussion.

    Thanks, Dan

    1
  • wilsonrice
    wilsonrice ✭
    January 5, 2023

    The search images method takes a few tries to figure out the necessary steps, but it seems to work. So far no lock ups or error messages. I won't be going back to the other way to search.

    0
  • Paul W
    Paul W ✭✭✭✭✭
    January 5, 2023 edited January 5, 2023

    @Mike357

    Before you shut this thread down, perhaps you could provide an update from the engineers as to whether they are still working to resolve the issue, or if the "workaround" of viewing pages from the Images section of FamilySearch is likely to be the only way to deal with this problem for the foreseeable future?

    1
  • Stephanie V.
    Stephanie V. ✭✭✭✭
    January 5, 2023

    Hi everyone!

    Just a heads up that we are not going to close this conversation as of yet as there are people watching it to keep updated and aware of what the community is saying. We are still working on resolutions and trying to get some better answers from the engineers and are grateful for your continued patience. We all feel your pain and frustration and so appreciate you hanging in there with us as we seek to figure this out.

    Thanks!

    -Stephanie 😊

    2
  • Alison Wilson_2
    Alison Wilson_2 ✭
    January 8, 2023

    9 January 2023 - in Australia still having this "error loading images" problem. tried the workaround with the Image viewer - same thing - crashes after viewing a few images.

    2
  • guy_przytula
    guy_przytula ✭✭
    January 15, 2023 edited January 15, 2023

    even with new image viewer we have a similar problem

    image.png

    best regards, Guy

    2
  • Mike357
    Mike357 ✭✭✭✭
    January 15, 2023 edited January 15, 2023

    @guy_przytula ,

    Including a URL link is always more helpful than sending just a screen shot; however, I think that I was able to see enough of the URL to derive that you were searching Images for the location, Malderen, Brabant, Belgium. I was able to make, what I believe is, the same search without problem. Here's the URL for my search:

    https://www.familysearch.org/records/images/image-details?page=1&place=10306373&endDate=1848&startDate=1845&rmsId=TH-266-11867-72954-94&imageIndex=0

    I mentioned, earlier in this thread, that FamilySearch uses throttle to protect the system. Often, when the throttling limit is reached, an error code 429 is generated. The system then requires that you wait some period of time before retrying. However, the amount of time that is required before another search of the collection will be success seems excessive. Hopefully, we can get a team to look at this issue.

    In the meantime, it is suggested that we clear cookies and cache, wait for a few minutes and retry the search. When we need to page through images of a document, as is sometimes necessary dependent on the document, it is suggested that we "slow down" so as not to approach the throttling limit. I understand that several minutes to hours is more than excessive as a retry time-out (and many of us have experienced this), but in some situations this may help.

    It is unusual that you are finding this problem in Images, as it has, somewhat consistently, been suggested as a alternate to a records search that will not produce the throttling problem.

    We will continue to work on getting the review and resolution on this issue that is needed. Please let us know, when you may get your search to work, what you did differently to get there.

    1
  • StevenMartin61
    StevenMartin61 ✭✭
    January 17, 2023

    Another month & this issue is STILL not resolved. As I stated in an earlier note, it seems that this 50 to 60 image limit was intentionally added by Family Search. Probably to push us to the other image viewer. I can not believe that Family Search's IT dept. can not find a solution to this "problem". This has been going on for about 6 months, but there was a period from Oct. to Nov., I believe, where this issue disappeared. Clearly, IT knows how to deal with this problem.

    Some users have had success with other image viewer. However, the images linked in the usual catalog send you to the usual image viewer. That catalog allows for much more in depth searching for sources, while in the other image viewer, that catalog is only searchable by location & the results are a jumbled mess. Hope IT is not planning to get rid of the usual catalog page.

    Please fix this issue.

    StevenMartin61

    2
  • Justintaylor76
    Justintaylor76 ✭
    January 23, 2023 edited January 23, 2023

    This problem has not been resolved and has been affecting my research. I am getting awfully frustrated. We should not need work arounds. I have actually stopped looking through images because I am so When things work do not change them. What's fixed ain't broken! Why all these new interfaces and a new image viewer? I commented on here on November 29, 2022 and it is now January 22, 2022 and the issue still has not been resolved. Also they haven't promoted the new image viewer! (at least to my knowledge)

    3
  • Leslie Tomlinson_1
    Leslie Tomlinson_1 ✭
    January 28, 2023

    What can we do to escalate this issue?

    1
  • Ken Spratlin
    Ken Spratlin ✭
    January 28, 2023

    The search images method does not work for me.

    Searching for image 29 of  008192040 (which generated this link):

    https://www.familysearch.org/records/images/image-details?imageGroupNumbers=008192040&rmsId=TH-909-73340-89792-73&imageIndex=28&singleView=true

    I get an error box shaded red/pink with the text "! 429". Different method, same result.

    1
  • N Tychonievich
    N Tychonievich ✭✭✭✭✭
    January 29, 2023

    @Ken Spratlin Viewing images was down for a while yesterday (28 January). That is why you got the message you did. All seems to be working correctly again today. Please try again.

    0
  • localghost
    localghost ✭
    January 29, 2023 edited January 29, 2023

    I’m having this error(“Error loading error image try later”)

    now for two days constantly, no matter if it’s desktop or mobile. Also does not matter which film I try to browse(Hungary/Austria/Slovakia)

    Also refreshing the page goes to a black screen error jumping out of page view to view all pages

    I’m enclosing some photos of the problem and happy to send a video as well.

    In the video, I’m using an iphone with the lastest update(16.3)

    9D3BB33F-748A-4368-89CB-C31E7B86B87F.png 4D7D5FE9-34A4-488A-AEF6-5B869FE74542.png


    1
  • Lisa Meyer_1
    Lisa Meyer_1 ✭
    January 29, 2023

    I have not been able to view any images all weekend. I've tried logging out and back in, different browsers, my computer and iPad, and accessing images through saved links, records attached to profiles, the catalog, and the image viewer and I continue to receive an error message. My experience has been the same as described by ann1337.

    1
  • Stephanie V.
    Stephanie V. ✭✭✭✭
    February 1, 2023

    Please go to page 1 of this discussion for some updated comments from @Sam Sulser. As she mentions, we really are working to get some resolutions to this issue. We are so sorry, believe us, we feel your pain. 😔Please hang in there with us.

    -Stephanie😊

    0
  • StevenMartin61
    StevenMartin61 ✭✭
    February 2, 2023

    Stephanie,

    I'm very disappointed that my previous message was deleted. I don't expect this kind of behavior in the United States.

    Steven

    0
  • Stephanie V.
    Stephanie V. ✭✭✭✭
    February 9, 2023

    @StevenMartin61 I am really sorry that you feel that way but we have a responsibility to maintain the integrity of the Community and we do that by following the Code of Conduct. The post that was deleted simply violated the Code of Conduct. Additionally, you are now suggesting that we are censoring you and that is not what this is about. We ask all posts to be relevant to the current discussion and kind and this post was not that. We will continue to follow these steps for all our users and for your reference, here is a link to the Code of Conduct that you may review. Thanks for your understanding.

    -Stephanie😊

    PS- I do have an update from our engineers that will be posted below.

    0
  • Stephanie V.
    Stephanie V. ✭✭✭✭
    February 9, 2023 edited February 13, 2023

    Good news!!! We finally have some answers from our engineers, although you may not like what we found out. The system is doing what it was designed to do to protect FamilySearch from malicious behavior. It took us a while to narrow this down because the issue sounds simple but is actually quite complicated and involves lots of moving parts.

     As we have made our engineers aware of your pain, they were able to do some system optimization to help correct the issue. We all will be closely watching to make sure that we are headed in the right direction.

    We have decided to close this conversation so that we are able to clearly see new issues as they arise. If you continue to have this problem, we have a new discussion started. Please post your comments here at this link. https://community.familysearch.org/en/discussion/138960/error-loading-image#latest

     Again, thank you so much for your patience and understanding.

    -Stephanie😊

    2
  • Ejay A.
    Ejay A. mod
    May 26, 2023

    The engineers made some changes to this. Has anyone in this post had this issue in the last 30 days?  

    0
«1234»
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 44.7K Ask a Question
  • 3.6K General Questions
  • 598 FamilySearch Center
  • 6.8K Get Involved
  • 676 FamilySearch Account
  • 7K Family Tree
  • 5.5K Search
  • 1.1K Memories
  • 504 Other Languages
  • 66 Community News
  • Groups