300 reservation limit
we are now limited to a limit of 300 reservations less any shared with the temple. This is clear in the rule stated but it is not being applied correctly by FamilySearch. I have been blocked for being over 300 but have only 72 reserved and not shared. I have 532 reserved in total but 460 are shared with the temple leaving only 72. It looks like the program is set up to consider all the reserved and does not reduce the number by those that are shared with the temple. this means that the system is not working as explained in FamilySearch or in press releases. The intention is to prevent lists beyond what someone could do preventing access to them by others. Those shared with the temple are available to anyone through ordinances ready or other request. The way the system is now working is contrary to the stated purpose of the new rule.
Answers
-
Try resetting the FamilySearch cookies on your device. It sounds like something isn't in sync for you: https://www.familysearch.org/cookies
0 -
Sending a private message to @Gordon Manville to help solve this issue.
0 -
Thanks for your help. This did not fix it but someone explained how the list works and I now have the problem fixed.
0 -
Perhaps Familysearch, and those of us for whom the 300 limit may constrain, may find it more appropriate to not apply the limit to children who are waiting to be sealed to parents who have not yet been sealed together. That parent sealing may not be in the control of the patron with the child's name reserved, nor would it be appropriate to suggest there should be a rush to complete that child ordinance before the parent's sealing is completed.
1
