LCR Frequently Down

I've recently been called as the ward clerk. Every Sunday I try to get a few things off my to-do list, but LCR seems to always be bogged down and just spins until it eventually gives me an error. Should I just assume that it's going to be down on Sundays?

rosspmarchant wrote: Sun Jul 09, 2023 12:08 pm Should I just assume that it's going to be down on Sundays?

No, but if there is another time earlier in the morning or later in the evening, or on another day, when you can do things, I would recommend it.

Thanks for the tip

That doesn't work if you have a bunch of people waiting for Stake Temple recommend interviews on Tuesday evenings and Sunday afternoons. I have to be able to access the tools to print those and LCR has been more problematic lately.

That's frustrating. Sounds like they need to add some more servers!

It's down again right now.

Question for the mods: Do you have any contacts in the church IT dept such that feedback of this nature actually reaches people who can do something about it? If not, I don't need to keep whining on the forum

From what I understand, many of the contacts you'd be referring to, are also end-users with identical church callings as the rest of us, and subject to the same frustrations and limitations in their ability to perform what's required when they have to use LCR for their callings.

So I expect inside the church IT dept, there's a fairly good understanding of the scope and severity of these issues. And I would imagine they likewise provide this feedback up their internal communication channels to those higher-ups (possibly outside the church IT dept) who make decisions. But that's just what I've gathered from reading lots and lots of Forum posts on these types of subjects, others can chime in with their own perspectives.

jb007tas45 wrote: Tue Jul 25, 2023 9:16 am Question for the mods: Do you have any contacts in the church IT dept such that feedback of this nature actually reaches people who can do something about it?

Short answer, no. This is a user-to-user forum where we are able to share potential solutions because of our varied experiences using Church tools and services.

That said, the developers are also clerks and leaders who deal with the same challenges each Sunday in their own local unit callings. And based on their posts in the past and private messages I have received, they are well aware of the problem and are doing all they can to resolve the issues that are within their control.

The issues include more than server capacity. Those I have spoken with have said (and it has been posted here that) there is plenty of server capability. There are always challenges in making everything talk. A simple request goes to many places as it is processed and handled, and any disruption along the way will cause slowdowns. Last I heard the Church is still working diligently to move off of legacy computers and systems, some of which still handle daily requests from web inquiries.

They are well aware of load balancing and efficient communication between servers in handling requests and responses. They are human, and part of the distributed nature of the way requests are handled allows for some mistakes that are quickly fixed. And again, they can only do what is within their power to control.

I rarely mention this and a discussion on the subject would be ruled off-topic to the technical nature of the forum. This is my own personal opinion and I do not have any inside knowledge concerning it, other than decades of Church leadership experience and a lot of personal scripture study. I merely mention that it is wise to remember that there are forces in this world who would like to see the Church fail in its mission and are doing all they can to see to it. The adversary uses all means in his control to do this, including the same means the Church uses to fulfill its mission.

Use the feedback links and GSD resources that have been provided. It will help the developers know how widespread a problem may be. But my guess is that they will already know about the issue and have been spending time working to resolve it.