LCR Down

[tonynocchi]

It's been hit or miss (mostly miss) since just after noon Eastern. Tried to get stuff done between 1 and 2 PM eastern (our second hour block) but couldn't. Was able to log in about 2:10 and update some callings, now I can't get into anything 15 minutes later.

[lugreer]

LCR has been down for over 2 days. Very frustrating because I cannot print the new ministering assignments to hand out on Sunday. I realize it is Saturday, but if someone reads this - PLEASE FIX IT! None of my presidency nor can the Elders Quorum access LCR. 10/26/2024

[jdlessley]

I realize it is Saturday, but if someone reads this - PLEASE FIX IT!

The Tech Forum is user-to-user discussion and collaborative self help. No one here has the ability to do anything. The official support channel is through the feedback link found at the bottom of most Church website pages. You can use the link on a web page that will load. Just be sure to mention the web page that you are having difficulty with.

[russellhltn]

LCR has been down for over 2 days.

If that's the case, I'm surprised the forum isn't flooded with messages about it.

Have you tried using incognito/private mode in your browser?

[tonynocchi]

LCR has been down for over 2 days. Very frustrating because I cannot print the new ministering assignments to hand out on Sunday. I realize it is Saturday, but if someone reads this - PLEASE FIX IT! None of my presidency nor can the Elders Quorum access LCR. 10/26/2024

We have grown so frustrated with LCR that we (ward and stake clerks) have pushed feedback up through the Stake President to the Area Authority Seventy. I do the bulk of all clerk tasks (membership and finance) for our ward and my wife is the Relief Society President so we both rely on LCR quite a bit throughout the week and especially on Sunday to process tithing. I recommend others do the same and maybe we'll get the attention of people who can make decisions and implement solutions.

[rmrichesjr]

As a ward assistant clerk, membership, I use LCR in a web browser frequently to record ordinances, update information, etc. For me, it works quite reliably.

Is it the cookie build-up problem you're experiencing? If so, the best solution is to clear your browser's cache and delete Church-related cookies whenever LCR or other Church website functions start misbehaving.

If it's something other than the cookie build-up problem, if you can give a little more detail about what's happening, somebody might have suggestions to help.

[tonynocchi]

I can tell you with 99.9% certainty that it is a server capacity issue. I am the ward clerk for a ward in Georgia and because I'm retired and have no little ones to wrangle, I handle about 90% of all clerking functions for membership and 100% of clerk issues for finance. Our second hour ends at 2 PM eastern. We share an office with another ward that gets out at 11 AM eastern, but we each have our own computer for clerk functions. Our biggest issue is recording tithing after church but we have had issues with pretty much all functions. The other functions aren't pressing, I can put that stuff in during the week but once we start tithing, it's either going into LCR or the manual process which is way more time-consuming on Sunday and then you have to put it in the system when it does come up.

The reason I can nearly guarantee it is server capacity is because when the other ward has problems, we have problems (they usually only have problems if they stay later than noon). Not only that, when we can't access LCR on the church computer, we try to access it on our phones and run into the same issues we are seeing on the church computer. On top of that, I bring my laptop to church every Sunday to take notes in Ward Council and I can hotspot my laptop off my cell phone, completely circumventing the church computer and the connectivity in the church building and still run into the same issue.

The timing is also pretty consistent for us. Typically it is about noon eastern that LCR starts getting sluggish. By 1 PM eastern, it is generally between very sluggish and unusable.

[BrianEdwards]

I can tell you with 99.9% certainty that it is a server capacity issue...

I'll simply re-share a post from a different thread with the exact same discussion. Although the topic is both interesting and very relevant for clerks, everyone in the Forum is on the outside and just guessing:
Having seen this recurring issue be discussed consistently over the years, my outsider's impression is...

[davesudweeks]

I can tell you with 99.9% certainty that it is a server capacity issue...

I'll simply re-share a post from a different thread with the exact same discussion. Although the topic is both interesting and very relevant for clerks, everyone in the Forum is on the outside and just guessing:
Having seen this recurring issue be discussed consistently over the years, my outsider's impression is...

And there is a post on the forum from a church employee (a year or two ago, I think) that stated that church leadership was well aware of this and if the problem was as easy as bandwidth or server capacity, the church would have resolved it long ago. My (unprofessional) opinion is there is some software constraint that causes the problem that is not an easy thing to address. But none of us know so the best thing we can do is be patient.

[tonynocchi]

I can tell you with 99.9% certainty that it is a server capacity issue...

I'll simply re-share a post from a different thread with the exact same discussion. Although the topic is both interesting and very relevant for clerks, everyone in the Forum is on the outside and just guessing:
Having seen this recurring issue be discussed consistently over the years, my outsider's impression is...

And there is a post on the forum from a church employee (a year or two ago, I think) that stated that church leadership was well aware of this and if the problem was as easy as bandwidth or server capacity, the church would have resolved it long ago. My (unprofessional) opinion is there is some software constraint that causes the problem that is not an easy thing to address. But none of us know so the best thing we can do is be patient.

As far as being patient, I have to wonder what the opportunity cost is in lost ministering time because we're struggling with mandated administration functions. When we are tying down a member of the bishopric for an hour or more after church to do something that should be able to be done in 15 minutes or less (not including the run to the bank to deposit) we are losing valuable time that could be spent meeting with families or members or focusing on the bigger picture. In the stake I'm in it's enough of a problem that the Stake President is pushing it up the chain.