FamilySearch. What was "Unexpected Error" all about, this morning, Fri.27March2020? What happened? T
LegacyUser
✭✭✭✭
Brett said: FamilySearch
Question:
What was that "Unexpected Error" all about, a short while ago, this morning, Friday 27 March 2020 [ie. Australian Eastern Daylight Time (AEDT), UTC +11]?
What happened?
Too much User/Patron usage/load, perhaps!
Just curious.
'Thank You in advance.
Brett
.
Question:
What was that "Unexpected Error" all about, a short while ago, this morning, Friday 27 March 2020 [ie. Australian Eastern Daylight Time (AEDT), UTC +11]?
What happened?
Too much User/Patron usage/load, perhaps!
Just curious.
'Thank You in advance.
Brett
.
Tagged:
0
Comments
-
Brian Jensen said: Sorry for the interruption. We had a networking issue that has been resolved.0
-
Tom Huber said: Good to know that has been resolved.0
-
Brett said: Brian
'G'Day', morning from "Down Under".
'Thank You' so much for responding; and, that advice.
Good to know it was not due to extensive use due to the current worldwide pandemic.
I would like to commend "FamilySearch", the platform has been reasonably stable considering the current worldwide pandemic; and, considering the undoubtedly extra heavy usage/load - well done.
Again, 'Thank You'.
Brett
.0 -
Justin Masters said: Is there any indication that FamilySearch usage is up during the pandemic?
I've been promoting it in my ward... but... I don't get a lot of requests for assistance from the ward members, although our usage stats were up year over year.
As I mentioned in a comment on a youtube channel... I am "that guy" that always mentions family history work in nearly every conversation at church.... because people talk about something being wrong with me if I don't. LOL0
This discussion has been closed.