Lost Ordinances

LegacyUser

Dixie Cragun said: When I look at my fan chart, I've noticed that around 5 of my grandparents have now lost their sealings to each other and are showing as green, needing these sealings done. I noticed this last night, with 2 sets of grandparents, now it has increased! Is there a bug in the program? These sealings were done years ago. Sealings to parents are also being lost.

LegacyUser

Tom Huber said: No ordinances are lost -- they are maintained by the Temple Department of The Church of Jesus Christ of Latter-day Saints.

But...

For a fairly long period of time, Patrons could enter ordinance data into the system. This included the IGI and was reflected in the dates in the Ancestral File and Temple Ready system.

FamilySearch came into being about a decade or so ago and at some point, the profiles in FamilySearch FamilyTree were matched up against the Temple Ordinance database. At that point, ordinances which previously were thought to have been completed may have had the dates disappear.

Bad merges may also have impacted the system.

See the article, "What should I do when ordinances are missing in Family Tree?" at https://www.familysearch.org/help/hel... (you will need to be signed into FamilySearch) for possible explanations as well as instructions on what to do.

LegacyUser

Gordon Collett said: To see if this is a problem in the program the engineers will need to know the couples involved. You will need to post the ID numbers of at least one set.

A common problem with "vanishing" ordinances is incorrect merges or someone switching out one or both of a couple with a duplicate instead of merging. Check the change logs for these couples and see if anyone has been doing some merges and accidentally switched out one set of grandparents for another or only merged one of the couple and "lost" the other or made any other changes that could have affected relationships.

Again, posting the IDs of a couple or all of these will let others here help you figure out what is going on and how to fix it. Since last night it was two sets and now it is three sets, it really sounds suspicious that you have a close relative who is doing some editing in Family Tree and is doing something incorrectly.

LegacyUser

Christina Sachs Wagner said: There seems to be a glitch in the system. Several people in a FB group have noticed this with relatives of theirs. Call the support line.

LegacyUser

Dixie Cragun said: Donald Daniel Ross 26L8-TXL and his spouse Joanna Hartsgrove KL6X-SQP. He did have a merge done yesterday. I restored that duplicate, but it didn't bring back the sealing date. Another grandparent, Charles L Saunders L8MB-CDY. He lost his SP and to both his spouses' sealings. His last merge was done on Dec 5, 2017. Richard Slater KWV3-YNW and Ann Corbridge KWVL-9JR. Richard's last merge was done on Nov 23, 2008. Ann's last merge was May 30, 2017. All those sealings were there last week.

LegacyUser

Cindy Hecker said: I noticed this too with one of my polygamist ancestors who married his wives while living. The SS were available. I reported yesterday and support replied and fixed today. Must be a bug, but definitely report so they can find the problem. I too have seen several post in FB groups about ordinances disappearing.

LegacyUser

Amy Archibald said: Contact FamilySearch Support so they can resolve this issue. I checked in Beta and all the Sealings you mentioned are listed there. So this is a bug of some sort.

LegacyUser

JT said: Loss of Sealing-to-Spouse has recently happened to my pioneer great-grandparents (both husband & wife) and two more generations back, including sealing-to-parents lost:

KWCH-CMV James Hunt (Jr.) 1872-1944 (both spouse and parents sealings lost)
KWJQ-SQP James Hunt (Sr.) 1850-1910 (just spouse sealing lost - wife's included)
L56Q-JCG Isaac Harrison 1819-1895 (both spouse and parents sealings lost)

I think this is a major bug to be fixed, happening to thousands of users. They shouldn't have to make us all open individual cases. But I will anyway.



But the old sealings have been fixed in the Beta version. Normally I expect the Beta version to be buggier than the Production version, not vice-versa.

LegacyUser

Don M Thomas said: Related Feedback:
https://getsatisfaction.com/familysea...

LegacyUser

Don M Thomas said: Related Feedback:
https://getsatisfaction.com/familysea...

LegacyUser

JT said: This has now apparently been fixed, at least by a quick look at my fan chart in ordinances mode - my 3 generations of pioneer ancestors now have their sealings done (such as in 1897 & 1920).

But it sure would be nice if FamilySearch could indicate what action (if any they know of) was taken to resolve this serious issue. Or at least to indicate from their end that it's been solved. Sure, many of us may not understand the technical issues involved, but many of us will get a good idea. Some divulgence will engender more confidence in the system.

LegacyUser

gasmodels said: All we can do is speculate. It appeared to me the issue was simply a display issue where records had been merged and somehow the system was not acknowledging that the merged ordinances existed and therefore they were not displaying sealings appropriately. I'm sure there is a much more technical reason for the issue (it might have been a buggy code update) but it appears that the few I had in my fan chart have been resolved also.

LegacyUser

JT said: No merges had happened on those. I opened a case on it last night. Now I got this reply on that case closure:

"There was a system issue. The engineers were able to resolve the problem."

LegacyUser

Jeff Wiseman said: I believe that this was also announced over in the Communities somewhere.