if I find a glitch and can tell when it started, will that help the engineers to find and fix it?
We have been battling a glitch for almost two years now that inserts the wrong man (with a similar name as our great grandfather) as the husband of our great grandmother. Every time, we have deleted the relationship, but it happens every few months (I can tell from the incorrect individual's change log).
We think we have figured out what is happening, and it's definitely a glitch.
If I give more details and the date it happened the first time, can the engineers find it and fix it?
Best Answer
-
@KathleenDaltonWoodbury I'm pretty sure I know what is happening here. When a new user creates an account, if they are a member and provide their membership #, the program will see if their membership record has family members info, like parents. It will create these family members, including living, possibly going back many generations. This way the new user has a pre-populated tree via membership records. This looks like there is an error in membership tree data and would need to be fixed - otherwise every new member that creates an FS account will replicate the wrong info.
Also, when that new user create their account, it shows them as the contributor, even though underneath is a FS process pre-seeding that tree by creating those persons.
I have created a defect to be investigated get the data fixed. Thank you for your post - as getting this fixed will help future users, and those related to this tree.
5
Answers
-
I'm in Engineering at FS and I would like to investigate. Could you provide here, or to me, the PID and any specific details. Thanks
3 -
The problem first happened on 21 May 2023, and has happened every month or so since then.
On 29 April 2025, my granddaughter (username removed) created a FamilySearch account so that she could see how she is related to a particular ancestor (Philo Taylor Farnsworth, who invented television, is my first cousin twice removed, and she is writing a school report on him). As soon as she put in her membership number, the FamilySearch Family Tree software created records for her mother (who is living) and me (also living) to connect her to my deceased mother's record on the tree.
Once she was able to get a screenshot of the relationship page showing how she is related to Philo Taylor Farnsworth, she exited FamilySearch, and thought nothing more about it.
On 30 April 2025, my sister notified me that this granddaughter had married an incorrect individual (Michael J Dalton L2TS-17T) to our great grandmother, although her correct husband (Michael Dalton L4N8-4SM) is still shown as her husband (with the same marriage date). We have struggled with this individual being added to our part of the tree every so often for years. I have called FamilySearch assistance more than once about this, and so has my sister.
We now realize that somehow the FamilySearch Family Tree software, in the same or a connected action as creating new living records to connect my granddaughter to her deceased ancestors on Family Tree, has inserted this incorrect individual into our great-grandparents' marriage, and this time, blamed it on my granddaughter (username removed) as anyone can see in the Change Log.
We didn't know that the software would automatically create living people records as it did to connect my granddaughter to the FamilySearch Family Tree, and when I called FamilySearch assistance, the person I talked to didn't know this would happen either.
Apparently, there is a glitch that is part of that automatic creation of living people that also puts Michael J Dalton (L2TS-17T) in my great-grandparents' marriage, and apparently, every time someone descended from my great-grandparents creates a FamilySearch account, this has happened.
So, two possible problems here:
If the FamilySearch software is not supposed to automatically create living people records to connect a new account to their ancestors, that needs to be looked into.
If the software is supposed to do this for new accounts, then there is a glitch that is causing it to insert an incorrect individual into a part of the Tree where he does not belong, and that needs to be looked into.
I hope all of this makes sense.
These are the other times this has happened (taken from Michael J Dalton's change log)
If you check the pedigree for each of these, I think you will see that they are all descendants of Michael Dalton (the correct one) and his wife Mary McFadden.
(username removed) 12 March 2025
(username removed) 8 February 2025
(username removed) 10 November 2024
(username removed) 26 September 2024
(username removed) 19 August 2024
(username removed) 5 May 2024
(username removed) 17 March 2024
(username removed) 25 July 2023
(username removed) 14 July 2023
(username removed) 14 June 2023
(username removed) 21 May 2023
Thank you for any help you can give us on this.
0 -
Mod note: Community is a public online forum. Your post was edited to maintain the privacy of living people. Please see the Community Code of Conduct for more details.
2 -
Thank you, Ashlee C
I didn't know how to send the details directly to Joemartel - I guess I should have asked him if there was a way to do it without including the information you have redacted.
I hope there is still something that can be done to fix this.
0 -
I sent the information to him in a private message before it was redacted. You can always send a private message to any user of the Community by clicking on the envelope button on the top right of your screen.
0 -
Thanks you Kathleen and Ashlee. I'll start looking into it.
0 -
Thank you Joemartel. I really hope this solves the problem.
And thanks to Ashlee for helping me with private messaging.
0 -
He said no found my family tree
0 -
Hello @Seif764, can you clarify your question please?
0
