Failing search for 1910 and other US Census
Previously, I have been able to search for historical records by entering the name and place, then limiting the results to certain collections by using the "Collection" button at the top of the results page. Now, if I click that button and select all census, it gives results. However, if I choose any combination of individual US Censuses from 1880, 1910, 1920, etc., the search fails, "Something Went Wrong."
Search for all Fullen in Virginia, https://www.familysearch.org/search/record/results?q.anyPlace=virginia&q.anyPlace.exact=on&q.surname=fullen, Works
Search for all Fullen in Virginia in all censuses, https://www.familysearch.org/search/record/results?count=20&q.anyPlace=virginia&q.anyPlace.exact=on&q.surname=fullen&f.collectionType=0, Works
Search for all Fullen in Virginia in 1910 census, https://www.familysearch.org/search/record/results?count=20&q.anyPlace=virginia&q.anyPlace.exact=on&q.surname=fullen&f.collectionId=1727033, Fails
Selecting just the 1910 US Census collection, https://www.familysearch.org/search/collection/1727033, and searching for Fullen and Virginia, https://www.familysearch.org/search/record/results?f.collectionId=1727033&q.anyPlace=Virginia&q.surname=Fullen, Fails0
I wonder if you need to clear you cache and cookies.
Thank you for investigating this issue. I certainly can't argue with your screenshots. I cleared both cookies and cache in Firefox and still no improvement. I just installed Chromium (the open source version of Chrome) and it, too, is failing in the same way.0
I just tested searches 3 and 4 in Firefox 111, Windows 10, both fully updated, and I also see 499 and 684 results, respectively.0
I just tried it on another computer. I am able to search other individual collections. The collections that fail are US Census 1850, 1860, 1870, 1880, 1900, 1910, 1920, and 1930. (US Census 1790-1840, 1940, 1950 all work) Since most collections work, I am baffled why these don't.0
Áine, Thank you for trying it, too.
I just tried two more things:
Restarted computer - Fails
Installed Chrome and tried it on Chrome - Fails0
I tried these searches again this morning and they all work now. If the FamilySearch engineers have any explanation, I would love to hear it. But, yeah, it works now.0
Yay! I'm glad it is working.1
Searching these censuses is not working again. However instead of getting the "Something Went Wrong" message the search just spins endlessly with no results. Selecting all censuses or other individual collections works fine.0
I just tested the 1910 US census, searching broadly for John Smith with no state or other fields specified. It took a moment, because that's a LOT of data, but the search returned 69,763 results.0
Áine, Thank you very much for testing this. I would really like to figure this out because I use census data all the time. - Anne1
FYI - I made that search on Firefox, Windows 10 - both fully updated. That's my usual browser.
Just now I made the same search on Chrome, same Win10 computer, and the results are the same - 69,673 John Smiths.
I've had some recent problems with Firefox on other sites, since the last update to Firefox, but not on FamilySearch.
Anne, since we cannot seem to replicate your problem, I think getting a personal appointment with Support is next step. You can find Contact Us in the Help popup when you click on the circle with a question mark in the top right corner in FamilySearch or Community. Here is a direct link as well. https://www.familysearch.org/en/fieldops/united-states-and-canada-contact-us1
Thank you for the recommendation to set up a Support appointment, which I will pursue.
To document today's experience, the census search worked fine again first thing this morning (Eastern Time) for a couple hours, then began to fail. I used just Chromium. I just tried Firefox, which I have not used all day, and had this same census searching issue. To me, is seems like an issue with the server, since there is nothing different happening in my browser use and deleting the cookies has no effect. It would take someone knowledgeable about the server and collections to figure out why this occurs for only certain census collections.