The Program that cried "Wolf"

Discussions around using and interfacing with the Church MLS program.
rpyne
Member
Posts: 227
Joined: Fri Jan 19, 2007 1:13 pm
Location: Provo, Utah, USA

The Program that cried "Wolf"

Postby rpyne » Mon Nov 22, 2010 9:13 am

Since the conversion to CUBS, every time I log in to MLS it tells me that I have an urgent task. When I open the urgent task list, it says I have changes that need to be transmitted. It doesn't matter how long it has been since I last transmitted nor how long since I last logged out.

I have tested it by repeatedly transmitting, logging out and immediately logging back in. Every time, the urgent task is there. I had hoped that 3.2.4 would fix the problem, but it hasn't.

Is anyone else experiencing this or is this an anomaly?

Like the villagers in the story of the boy who cried wolf, I am quickly getting to the point of completely ignoring the urgent task notice, especially since we have such old, slow computers that it sometimes takes more than a minute to open the urgent task window.

User avatar
aebrown
Community Administrator
Posts: 14691
Joined: Tue Nov 27, 2007 8:48 pm
Location: Sandy, Utah

Postby aebrown » Mon Nov 22, 2010 9:32 am

rpyne wrote:Is anyone else experiencing this or is this an anomaly?


Our stake MLS doesn't have this problem. If it's been a few days since we printed a Recommend Activation Report, we get a reminder for that, but it's certainly not "every time" we log into MLS. Most times I login, there is no urgent task reminder.
Questions that can benefit the larger community should be asked in a public forum, not a private message.

lambertinut
New Member
Posts: 9
Joined: Sat Oct 23, 2010 9:12 am
Location: Logan, UT

Postby lambertinut » Mon Nov 22, 2010 9:50 am

We too are having this problem in our ward. I haven't contacted the stake clerk yet to see what he can do to help. I also have done several send/receives, and it still shows up. I believe we had a problem with transmission, and it got hung up and didn't go through that night. I tried it again another night and it went through, but the message remained and will not clear no matter how many send/receives I do.

dentkev
New Member
Posts: 4
Joined: Fri Oct 24, 2008 2:43 pm
Location: Saratoga Springs UT, USA

Call support

Postby dentkev » Mon Nov 22, 2010 12:03 pm

I had this problem once. I called support and they knew how to fix the problem. The fix was quite simple, but I don't remember what it was.

User avatar
drporray
New Member
Posts: 13
Joined: Mon Jun 15, 2009 9:14 am
Location: Orem, Utah
Contact:

Postby drporray » Tue Nov 23, 2010 12:07 pm

I have also had this message appear for the last week or two. I called Salt Lake last week and they said it is a known problem and will be fixed as soon as they can. Of course it hasn't yet so I guess it's not high on their priority list.

rpyne
Member
Posts: 227
Joined: Fri Jan 19, 2007 1:13 pm
Location: Provo, Utah, USA

Postby rpyne » Wed Nov 24, 2010 9:35 am

dentkev wrote:I had this problem once. I called support and they knew how to fix the problem. The fix was quite simple, but I don't remember what it was.


I tried to call support last week on another issue and finally gave up after more than two hours. I can't spend that much time sitting in the clerks office when I need to be working.

atticusewig
Member
Posts: 308
Joined: Fri Jan 19, 2007 9:48 am

We need a public MLS known Bug list

Postby atticusewig » Wed Nov 24, 2010 11:58 am

Due to increasing call volume at CHQ, shouldn't the
known bugs in MLS be made public or at least
behind authorization (like new.lds.org/leaders) ?

A website clerks could access that documented
known MLS bugs and their effects and possible
workarounds could greatly reduce calls to CHQ.

This forum is a great start, but I'm sure the
developers already have a list of bugs to patch,
so if they could simply provide that list, the
community could fill in tricks on mitigating the
effects of the bug until the patch is provided,
to ease the demands placed on Local Unit Support.

- Atticus

Freedom55
Member
Posts: 83
Joined: Sun Nov 01, 2009 9:15 pm
Location: BC, Canada

Postby Freedom55 » Wed Nov 24, 2010 9:08 pm

I agree. I've asked CHQ a couple of times in the past for a "bug list". It would not only save calls to them but it would save some calls to me from the ward clerks. The response has always been, "Sorry, we don't have a list". :confused:

rpyne
Member
Posts: 227
Joined: Fri Jan 19, 2007 1:13 pm
Location: Provo, Utah, USA

Postby rpyne » Wed Dec 01, 2010 7:21 pm

dentkev wrote:I had this problem once. I called support and they knew how to fix the problem. The fix was quite simple, but I don't remember what it was.


Interesting. I just got off the phone with MLS support and was told that starting with 3.2.3 the message is there by design.

As I told them, if there ever is anything urgent, from now on it will be ignored.


Return to “MLS Support, Help, and Feedback”

Who is online

Users browsing this forum: No registered users and 1 guest