I just attempted to move in a record, and received this response....In my 15 years as membership clerk, this is a first! What does it mean?
"An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error."
Moving Record Problem
-
- Senior Member
- Posts: 1295
- Joined: Thu Jan 24, 2008 4:34 pm
- Location: Las Vegas, NV
-
- Community Moderators
- Posts: 4321
- Joined: Thu Jan 25, 2007 11:32 am
- Location: Dundee, Oregon, USA
Re: Moving Record Problem
There's nothing in that response that would be very useful for a clerk. It's just saying that the something got messed up during processing of the request and/or returning information to you stating that the operation had succeeded. The root cause of the error condition might be a bug in the software, a network glitch, or something similar.
I'd recommend closing that browser window, clearing your browser's cache, deleting Church-related cookies in your browser, and going back into LCR. If the record got moved, all is well. If the record did not get moved, then you could try the operation again. If that fails, it is probably time to call the support line or contact GSD.
I'd recommend closing that browser window, clearing your browser's cache, deleting Church-related cookies in your browser, and going back into LCR. If the record got moved, all is well. If the record did not get moved, then you could try the operation again. If that fails, it is probably time to call the support line or contact GSD.
-
- New Member
- Posts: 3
- Joined: Thu Oct 02, 2025 1:23 am
Re: Moving Record Problem
That looks like a server-side error in LCR rather than anything you did wrong. The “digest” message just means the system hid the technical details.
I’d try again later or clear cache / switch browsers to rule out a local glitch. If it still happens, use the “Feedback” or “Report a Problem” link in LCR so Church IT can check the backend logs.
I’d try again later or clear cache / switch browsers to rule out a local glitch. If it still happens, use the “Feedback” or “Report a Problem” link in LCR so Church IT can check the backend logs.