Anyone else having problems Deleting or Removing either Parent-Child or Couple relationships?
Is anyone else having problems Deleting or Removing either Parent-Child or Couple relationships?
We have been trying to Delete or Remove both Parent-Child or Couple relationships, that are Incorrect; but, after adding a Reason and selecting Delete or Remove, the Relationships are Not Deleting or Removing, even after Refreshing.
This has been happening over a number of days, of late.
On occasions, able to Delete a Child, from one Parent; but, not the other.
Have tried a number of different Parent-Child and Couple relationship, that are not related, through various Users.
Have help from experienced Users, no one understans why.
Operating System is Windows10, up-to-date as can be.
Various Browsers (eg. Chrome, FireFox, Brave), all up-to-date.
Clearing Cache and Cookies and Browsing History, makes no difference.
PS: Forgot to add, that the Changes show up in various Change Logs; but, Changes Do Not appear.
Answers
-
If your reason statement is too long, it can cause the detach process to fail.
See this recent thread:0 -
@ShelleWells
A number of users and a number of PIDs.
@Áine.ní.Donnghaile
Thanks.
But, Reasons are not too long.
The full Reasons appears in the various ChangeLogs.0 -
@ShelleWells
Will message you privately, after further testing,1 -
@ShelleWells
No need to private message you.
After testing, here is information, for the Programmers after testing.
BUG
Scenario 1 - "Parent-Child" Relationship
First Reason attempt that all appeared in ChangeLog; but, Did Not Delete the Relationship.
.
.¶
DELETE "Parent-Child" Relationship.¶
INCORRECT "Parent-Child" Relationship.¶
This Child indicated as Born in Lithuania.¶
Whereas; ALL Other Children, for this Couple, Born in Centerville, Davis, Utah, United States of America.¶
This Child DOES NOT relate to this Couple.¶
Ends.¶
.¶
.
Second Reason attempt that again all appeared in ChangeLog; but, again Did Not Delete the Relationship.
[ Simply removed the "¶" mark, thought Special Characters may have been the problem ]
.
DELETE "Parent-Child" Relationship.
INCORRECT "Parent-Child" Relationship.
This Child indicated as Born in Lithuania.
Whereas; ALL Other Children, for this Couple, Born in Centerville, Davis, Utah, United States of America.
This Child DOES NOT relate to this Couple.
Ends.
.
Third and final Reason attempt that again all appeared in ChangeLog; but, Did finally Delete the Relationship.
[ Simply removed the ALL the Lines ( and without the "¶" mark) and making it one single Line ]
DELETE "Parent-Child" Relationship. INCORRECT "Parent-Child" Relationship. This Child indicated as Born in Lithuania. Whereas; ALL Other Children, for this Couple, Born in Centerville, Davis, Utah, United States of America. This Child DOES NOT relate to this Couple. Ends.
Scenario 2 - "Couple Relationship"
First Reason attempt that all appeared in ChangeLog; but, Did Not Delete the Relationship.
.
.¶
INCORRECT "Couple Relationship".¶
INCORRECT "Marriage Event".¶
Therefore, "Delete", this INCORRECT "Marriage Event".¶
Ends.¶
.¶
.
Second Reason attempt that again all appeared in ChangeLog; but, again Did Not Delete the Relationship.
[ Simply removed x4 Lines, left the Special Characters in place ]
INCORRECT "Couple Relationship".¶
INCORRECT "Marriage Event".¶
Therefore, "Delete", this INCORRECT "Marriage Event".¶
Ends.¶
Third and final Reason attempt that again all appeared in ChangeLog; but, Did finally Delete the Relationship.
[ Simply removed the ALL the Lines and making it one single Line ]
INCORRECT "Couple Relationship".¶ INCORRECT "Spouse".¶ Therefore, "Remove", this INCORRECT "Spouse".¶ Ends.¶
For the Programmers
So, it looks like its the Number of Lines; and, Not the number of Words or Characters, is the problem, making the Detection/Removal Not work.0 -
@ShelleWells
Have just checked, we now finally have access, to the Beta environment, again.
Will show the issue there; and, provide the necessary PID, in the Beta environment.
Hopefully it should generally work the same, within reason.0 -
@ShelleWells
BUG
For the Programmers.
BETA FamilySearch site.
PIDs
Father/Husband = BM3C-DHM
Mother/Wife = BM3C-4RX
Male Child = BM3C-7V6
Female Child = BM3C-79D
SAME things happened, as per the Scenarios above; EXCEPT, that the First and Second attempts, Did Not appears in ChangeLog, as per Main site.
So basically BOTH sites are almost identical.0 -
@ShelleWells
Reminder.
This is still happening.
Did the persons, that we provided, in the BETA FamilySearch site, help the Programmers?
Just curious.0 -
@ShelleWells PIDs on the beta site are most definitely NOT generated each time you access beta. Those PIDS that Jenny.B supplied are certainly still accessible by anyone on the beta site.
The only time beta PIDs become invalid is in the infrequent refresh of the beta data from production data, but that happens only once a year (or less). But beta PIDs will be reliable just like production PIDs until that happens (and that has not happened since 4 Feb 2026 when those particular beta PIDs were created).
2 -
Thank you for the clarification @Alan E. Brown
0 -
@ShelleWells This problem is easily duplicated on beta or production. The beta PIDs aren't really even needed, since the whole problem is that the deletion of the relationship is failing with certain reason statements. Because of that, there is nothing in the change log to see when the deletion fails. The PIDs are mildly interesting because they show when a somewhat similar deletion succeeds, but really the engineers need to examine what happens when the deletion fails.
Any engineer can see that the PUT call to
https://beta.familysearch.org/service/tree/tree-data/relationship/parent-child/{parent-child-relationship-id}/deletewith a payload like
{"reason":".\nDELETE \"Parent-Child\" Relationship.\nINCORRECT \"Parent-Child\" Relationship.\nThis Child indicated as Born in Lithuania.\nWhereas; ALL Other Children, for this Couple, Born in Centerville, Davis, Utah, United States of America.\nThis Child DOES NOT relate to this Couple.\nEnds.\n."}Results in "INTERNAL_SERVER_ERROR"
That is the scenario that the engineers need to examine. If a particular reason statement is not allowed, the response should not be an internal server error, but should be a clean error response so that the UI can then report the error in a way that gives the user guidance. An internal server error clearly shows that there is some sort of coding error in handling payloads like this.
3
