Oops. You’re moving too quickly. You may need to wait a moment and try again.
Why do I receive a page that pops-up with the two line message: "Oops. You’re moving too quickly.
You may need to wait a moment and try again."
It occurs with census pages and WW1 registration pages that I need to view in order to be sure that I have the correct relationships / person prior to adding the record, or to add to the indexed information.
I have logged out of my browser, cleared the browser cache, and then logged in without success. Here is a url for the most recent pop-up
It occurred when I had many windows open, and also then just a few.
Thank you.
Answers
-
Repaired URL: https://www.familysearch.org/ark:/61903/3:1:33SQ-GYYX-SNNR?cc=1968530&personaUrl=%2Fark%3A%2F61903%2F1%3A1%3A7YT1-LQZM
Note that 3 instances of %3A before the ? in your URL have been changed to colons. The Community platform will often corrupt the URL if you hit return/enter immediately after posting the URL in your post. And, we only need the part of the URL before the question mark https://www.familysearch.org/ark:/61903/3:1:33SQ-GYYX-SNNR to see the image of the record.
0 -
That did NOT answer my question. Today I performed the same actions and I was shown the expected record with no problems.
This successful record viewing has all the same three %3A in the copy and paste, but is displayed with colons in the address on the browser, just as the shortened url you displayed.
Is there a daily limit on activities on the website? If so why would I be restricted from viewing the original documents, yet still be allowed to make other changes?
Before posting I searched for the error message without success, thus the question. I have a screenshot of the message which I attach (I missed seeing that option earlier).
Screenshot 2024-11-10 at 23-14-22 FamilySearch.org Oops ....png
Thank you
0 -
As another user of the website, above my paygrade to answer your question. I have not seen the problem, and I'm on the site most of the day, most days.
0 -
I'm getting the same thing. It was a little quirky yesterday, but after reloading I was able to see the image.
Today I'm getting the "Oops. You’re moving too quickly" message.
No, I am not moving too quickly. I had this image bookmarked and was able to see it yesterday
https://www.familysearch.org/ark:/61903/3:1:S3HY-6QLG-KD?wc=M66P-SZS%3A40204801%2C40316601%26cc%3D1452409&i=330
1 -
I was looking at the 1900 and 1910 census records for Crockett Co, TN, but more specifically I cannot say. If it happens again I will keep better notes.
Note: User Frances McHugh (comment above) was in a database for 1883 that I have never accessed.
Last night the message popped up for another record, but after a few minutes I tried again with success. The previous evening I could not access the images for so long (greater than 20-30 minutes) that I gave up and left the computer.
It may have something to do with the level of the user, Áine Ní Donnghaile is level 5, I and Frances McHugh are at Level 1.
It strikes me as a security measure, that is triggered under certain user conditions, so someone in IT should have the answer.
0 -
@FLQR, those "ratings" are based on a user's history here in the Community. They bear no relation to the main FS site, and confer no privileges anywhere.
1 -
This morning I was looking at probate documents at The National Archives in London using FamilySearch, having signed in to my account. I used the catalogue to find the right probate court and the right dates. After searching for a while and looking at the wills with no problems, a message came up (as I was trying to go to the next page) that I was going too fast. I went out of the site and logged back in again but although I could get into the catalogue to find the court and date it would not load any wills. I tried on another computer and it was the same. I tried logging in using another account for FamilySearch but again nothing would load up
. I often use the site to look at wills so I know how it all works.
Has anyone got any ideas as to why this happened? I plan to go back next week so I am keen this does not happen again.
Many thanks.
0 -
I'm seeing this same message for Catholic records that I've been doing an extraction project on for the last month. I was just starting the last page when it hit me. I've been on a marathon the last few days to finish this for a woman who is finishing up her genealogy degree through pathways. Is there some kind of metering to keep automated bots from filling in junk? I mean, I've been working HARD on this the last few days, but….
I've trashed cookies, rebooted, and nothing works. I tried it from a system on a different IP and that seems to work, but I can't do this type of stuff from my work's computer.
https://www.familysearch.org/ark:/61903/3:1:3Q9M-CSVT-8SC5-W?i=729
0 -
This does sound like throttling at the IP address level but with a less than meaningful error message. Have you tried using a different IP address on your normal computer, e.g. via the hotspot on your 'phone?
2 -
Engineers believe they corrected this problem yesterday. Please report if anyone continues to receive this error message and is not able to view documents.
1 -
Thanks @SerraNola
0 -
Thank you. I was experiencing this problem all the way through 4:30 (PDT) am this morning as I was trying to do the last page of a volunteer effort. I had to work from a copy of an image I sent myself from a work computer and all the source attachments are looking like an external link. ( and look at the baptism record for Agnes Gertr. Hertel. The link shows:
).
I was using RecordSeek to assist as attaching sources within familysearch to multiple people is painful. (I couldn't access the images and UI for attaching sources)
But the bad thing I've noticed is that the image numbers have all changed now. If you look at the link you'll see i=729 on the end. (It WAS image 730 in the film yesterday!) but today's its image 660!! Which is too bad, as for the entirety of the linking project over the last month, we've been asked to put a reference to the image number in our source citation, and that's not even correct anymore - thank goodness the link still gets there.
But every one of the Christening "Reason This Information Is Correct" sections now says something like this:
"Baptism Record - Saint Peter Claver Catholic Church, Sheboygan, Wisconsin, United States
LDS Film # 008132880 Image 730"
And it's wrong now.
[LATE EDIT: It's NOW image 676!!! Why is it changing by the minute? and the link no longer points to the right page! It's off by 1.]
I'm attaching two screenshots taken minutes apart.
0 -
Agnes' baptism is on image 665 now, when I just looked at it.
https://www.familysearch.org/ark:/61903/3:1:3Q9M-CSVT-8SCT-H?i=664
0 -
It's literally changing by the minute! I updated the comment above to show it.
0 -
The Oops… message popped up again at 9:57 pm CST Nov 17, from a Research Help, the record
Cite This Record"United States World War I Draft Registration Cards, 1917-1918", database with images, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:7TRB-D53Z : 10 July 2024), Walter Coleman Johnson, 1917-1918.
displayed to the right of the person, LVTJ-8YR, attempting to view
https://www.familysearch.org/ark:/61903/3:1:33S7-9YBF-SSWG?cc=1968530&personaUrl=%2Fark%3A%2F61903%2F1%3A1%3A7TRB-D53ZI attempted again without success at 10:02 pm (right click, open in a new window), same pop up); ditto at 10:05 pm, 10:07 pm, 10:12 pm, 10:18 pm, 10:27 pm (30 mins, really much MORE than a moment IMHO), 11:11 pm, 12:08 CST AM Nov 17, Over two hours "waiting a moment" still without success!!Clearly whatever the engineers did it was insufficient.
I am leaving the Research Help prompt without completion.
-1 -
Not that it's any consolation, but this is what I get when I try that link:
1 -
When I've encountered throttling issues on FS in the past, 2 minutes was not nearly long enough to wait.
And repaired URL for the benefit of those who may try to help: https://www.familysearch.org/ark:/61903/3:1:33S7-9YBF-SSWG
0 -
The first line of my prior message at 12:12 AM should have the date corrected to read [ Nov 16 ] as in:
The Oops… message popped up again at 9:57 pm CST Nov 16, from a Research Help, the record …
0 -
I will try to get an answer for why this is still happening. Stay tuned……
1 -
Response from Engineering: "Obviously, we still have some work to do." They ask that if the message pops up again that you switch to Chrome Incognito or "new private window" in Firefox to help diagnose if the problem is connected to issues with your computer. This is especially important if you are using one or more browser extensions to try to speed up your work.
Still waiting for an answer on the peculiar fluctuation in the number of frames for DGS 8132880.
1 -
Receiving this problem re: Castellammare di Strabio Civil Records at 6:48 pm EST. "Oops. You're moving too quickly. You may need to wait a minute to try again."
Granted I was powering through marriage records, but was zeroing in on the names and working fast. @SerraNola I did as the engineers asked and tried in Incognito Mode (after logging in to my account). Same error message.
0 -
I get this almost daily and have been for a while. It's to the point of being annoying and ridiculous and it needs fixed.
0 -
@todd Paradine Thank you. This is good feedback. @StephenDespot Can you provide more details? Are either of you using a browser extension as you work?
0 -
@SerraNola Stephen's original thread is
I tried to help and directed him to this thread for more info.
0 -
@FLQR The issue is not limited to the recordset you were viewing. I encountered it today for the first time while viewing an entirely different set in the new viewer. However, in my case it seems that it exhibits the same behaviour as the old image viewer, in that once the error has occurred it does not reset after waiting a while.
I suspect that this is simply a new error message that replaces the old non-specific one. The latching error is unchanged though.
1 -
@SerraNola I'm just using the regular old Google Chrome browser. Nothing special. Sometimes when I get booted I can switch to Microsoft Edge and that will work but last night neither did. Once I'm kicked out of the catalogs, that's it. I'm out of all of them for a while. I waited almost two hours and did other things last night and it still was not letting me in so a nice productive night of research was thrown into the garbage. It's like we're limited on what we can see in a day. So far today all is well but who knows how long that will last. Go back to the old image viewer, please. It seems ever since you changed it we've had this problem. Clearing cookies and cache and resetting/rebooting everything did not work either so even if it did that's only a band aid and a temporary solution at best.
0 -
@SerraNola Resuts of Experiment concerning the error 'Latching'.
After I got this message, I signed out, cleared all browser data and restarted from power down. When I tried to use the image viewer, I got the this error immediately. OK, I thought, my account is still being recognized at the server end, and there's still a error flagged somewhere. So…
My friend came over and started from power up on my machine, logged in with her account and went to the same image URL. She got the same error immediately.
She signed out, cleared everything etc. etc. and I started again from power up. Tried to view an image: Guess what: same error message immediately.
I suspect that something at the server end or one of the 3rd parties that serves the content is fingerprinting, and when it doesn't like the activity it flags an error and logs the machine fingerprint as a nefarious actor. Nothing can be viewed until either this flag times out, or some intervention occurs that causes the error to be cleared. Either way, the user is scuppered for a significant period, not just "a while"
Users need to able to view images with ease because…
1: In many cases the actual image that needs to be viewed is not the one that is presented, so the user needs to move backwards and forwards to locate the correct one.
2: In many cases, other family members appear on separate images in the record set…. as above
3: In order to interpret some of the handwriting, it is necessary to find similar words or letters on multiple images for comparison
This latching problem is a real handicap.
1 -
Certainly seems to be confined to retrieving images. Nothing ever related to an indexed record or anything else. Been seeing this behavior for about a month or so. The 'Too Quickly' message is fairly recent. Often getting similar behavior with a 'Cannot Display Image Group' message or '502 Bad Gateway'. I've had luck switching browsers in the past [from Firefox to Microsoft Edge], but this morning Edge too was not working.
I'm a user of Tull Text Search and when attempting to view a result, you can sometimes see the desired page 'flash' very briefly and then you're given the error/problem message
Tried Firefox just now using Incognito mode and that seems to working as it should displaying the desired original record/document images
I don't have any specific data, but seems to be worse on the weekends
Hope that provides some more 'clues' for the engineers
1 -
Thanks to all of you for thoughtful feedback. I will compile and send in tomorrow.
1
