Do developers see the # of errors users get?

I know this forum isn't a monitored forum by the church but I do see employees on here so I have a question that may go unanswered.

Do the software developers know how many errors LCR displays to users? I know in many cases companies try to log the errors and trigger notifications to people about errors. However, I suspect in many companies those aren't seen by people that would really like to know about them.

The past 4 hours I've been trying to create a new child record. Just getting errors. I get errors a lot, on the expense pages, etc. Pretty much weekly I see a random error.

Earlier today the error was "something went wrong". Now it's a proxy error. (I'm a firm believer that all church developers and admins should also be ward clerks.

---
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request

Reason: Error reading from remote server

chriswoodut wrote:I know this forum isn't a monitored forum by the church but I do see employees on here so I have a question that may go unanswered.

Do the software developers know how many errors LCR displays to users? I know in many cases companies try to log the errors and trigger notifications to people about errors. However, I suspect in many companies those aren't seen by people that would really like to know about them.

The past 4 hours I've been trying to create a new child record. Just getting errors. I get errors a lot, on the expense pages, etc. Pretty much weekly I see a random error.

Yes, we log them. We're quite aware that there were issues yesterday.

chriswoodut wrote:Earlier today the error was "something went wrong". Now it's a proxy error. (I'm a firm believer that all church developers and admins should also be ward clerks.

You would be surprised at how that works out. I remember looking down the row once and counting two people who were former bishops, seven people who had been in a bishopric, six people who had served as a clerk but were not serving at the time, and three currently serving clerks.

Right now we have five currently serving clerks that I can think of off the top of my head.

scgallafent wrote:

chriswoodut wrote:

chriswoodut wrote:Earlier today the error was "something went wrong". Now it's a proxy error. (I'm a firm believer that all church developers and admins should also be ward clerks.

You would be surprised at how that works out. I remember looking down the row once and counting two people who were former bishops, seven people who had been in a bishopric, six people who had served as a clerk but were not serving at the time, and three currently serving clerks.

Right now we have five currently serving clerks that I can think of off the top of my head.

It makes me feel better knowing those that have the ability to try to resolve stability issues are experiencing the errors themselves. I see errors weekly. Hopefully management will give them the time to address the issues.

(Still getting the error on this new baby record 24 hrs since I first tried.)

chriswoodut wrote:(Still getting the error on this new baby record 24 hrs since I first tried.)

I was involved in some discussions earlier today about the changes they were making to address this. I don't know if they got finished today.

scgallafent wrote:

chriswoodut wrote:(Still getting the error on this new baby record 24 hrs since I first tried.)

I was involved in some discussions earlier today about the changes they were making to address this. I don't know if they got finished today.

I got it to save! They must have gotten it resolved.

I'm not able to connect to LCR this morning, and even Handbook 1 in GLO is problematic. This is the second week in a row, and I really need to get some clerking work done. Any suggestions? I've tried countless combinations of logging in and out, clearing my cache, using different browsers and devices, and clearing out cookies.

GuJiaXian wrote:I'm not able to connect to LCR this morning, and even Handbook 1 in GLO is problematic. This is the second week in a row, and I really need to get some clerking work done. Any suggestions? I've tried countless combinations of logging in and out, clearing my cache, using different browsers and devices, and clearing out cookies.

Ditto. A lot of errors today. I'm not trying to complain to be a jerk but I would love to see a sprint dedicated to stability.

This is a recurring issue that just seems to be gradually snowballing. With more things moving on to LCR, there simply does not seem to be enough server capacity to handle the load when Sunday morning arrives in the western US.

ammonlauritzen wrote:This is a recurring issue that just seems to be gradually snowballing. With more things moving on to LCR, there simply does not seem to be enough server capacity to handle the load when Sunday morning arrives in the western US.

It does seem to feel like a server load issue. I can get the generic error and refresh 5 seconds later and it goes through (on a good day). Weekdays are generally fine, which is probably when the programmers and staff are looking at it and not seeing problems.

We appreicate your frustration. I replied in another thread with the number of developers who are also regular Sunday users of LCR.

Having said that:

A sprint dedicated to stability isn't realistic. There are multiple teams scattered across the Church involved in this and the logistics of trying to sync up sprints for so many teams wouldn't make sense. Creating a sprint for it won't change behavior because it's already the primary focus of the teams involved. I know of quite a few people who ended up skipping our annual Christmas devotional with a member of the Presiding Bishopric on Friday because they were in the middle of working through a bunch of related issues.

"With more things moving on to LCR" doesn't adequately contemplate the complexity of the infrastructure involved. LCR is just one piece of what goes on on Sundays. Server load is involved, but it's not just a matter of adding more servers.

We've got engineers whose Sunday experience on occasion (or often) consists of the sacrament and then back to work. I know one engineer who went six weeks without going to church. When you're complaining about something not working on Sunday, remember that several people aren't getting a Sunday.

Trust me -- everyone involved knows there are issues and they're working on resolving them. The problems they're sorting out are some pretty complex interactions between multiple systems and they aren't trivial.

I don't doubt it is complex.  I've managed a software team and have many years system and network administration experience, so I do understand.   I don't say that to claim some sort of authority but to communicate that I do get it. I've been that guy that gets the phone call in the middle of the night about a server problem. I've been the guy at work on Thanksgiving because it's not a holiday where the customer is in Europe.

I also know that when nobody says anything, that wheel isn't going to get any grease because something or somebody else that is more squeaky will get the admin/dev time. (Before someone tells me to us the feedback link, I do use it and it feels like a black hole.)

Whatever the driving issues are (complexity, schedule, design, capacity), the end goal of using the system is being compromised the past couple of months. In voicing concerns I'm not criticizing but trying to provide feedback so those with decision making ability hear and know what the user experience is. Or even if the developers on here see the grumblings and next time they are in a meeting they have some context to the user experience.

Don't get me wrong, I really like the functionality we're getting.  I do appreciate the efforts.  I see the potential of the tools and so when I'm trying to use them and I'm getting errors, I want to provide feedback.

System is really bad today. Proxy errors.