Home› Welcome to the FamilySearch Community!› FamilySearch Help› Temple

Sharing reserved names with family & friends

Tom J. McVey
Tom J. McVey ✭
September 12, 2021 in Temple

For the past 5 or 6 days I've not been able to share reserved names with family or friends. I've been getting a message "Please Try Back Later", "We are unable to retrieve reserved names at this time."

Is anyone else having the same issue?

Is F/S aware of the issue?

Suggestions, I've be "Trying Back Later" with no success!


Thanks,


Tom

0

Answers

  • DMS1737
    DMS1737 ✭✭✭✭
    September 12, 2021

    Thank you for contacting FamiySearch Community. Your question has been forwarded to a specialty team for review and resolution. You may be contacted by that team if they need to gather more information.

    Thank you

    0
  • Ashley Camille Crummett
    Ashley Camille Crummett ✭
    September 14, 2021

    Was there an answer to this? I'm getting the same error message: "Please Try Back Later", "We are unable to retrieve reserved names at this time."

    0
  • Tom J. McVey
    Tom J. McVey ✭
    September 15, 2021

    No answer yet...no surprise there! I keep trying multiple times during the day! I've got open sharing emails with no less that 10 relatives or friends right now that can't be cleared up. Yes, after 2-weeks they go away but some of these folks have been counting on these shared ordinances to take to a reserved appointment.

    Thanks for responding.

    Tom

    0
  • DebDT
    DebDT mod
    September 15, 2021

    Thank you for your post. Our engineers are aware of the problem and working to correct. We appreciate your patience.

    0
Clear
No Groups Found

Categories

  • 23.8K All Categories
  • 513 1950 US Census
  • 46.8K FamilySearch Help
  • 100 Get Involved
  • 2.3K General Questions
  • 347 Family History Centers
  • 347 FamilySearch Account
  • 3.4K Family Tree
  • 2.6K Search
  • 3.7K Indexing
  • 452 Memories
  • 4.6K Temple
  • 265 Other Languages
  • 29 Community News
  • 5.5K Suggest an Idea
  • Groups