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.
The Program that cried "Wolf"
-
- Member
- Posts: 228
- Joined: Fri Jan 19, 2007 1:13 pm
- Location: Provo, Utah, USA
- aebrown
- Community Administrator
- Posts: 15153
- Joined: Tue Nov 27, 2007 8:48 pm
- Location: Draper, Utah
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.rpyne wrote:Is anyone else experiencing this or is this an anomaly?
Questions that can benefit the larger community should be asked in a public forum, not a private message.
-
- New Member
- Posts: 9
- Joined: Sat Oct 23, 2010 10:12 am
- Location: Logan, UT
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.
-
- New Member
- Posts: 4
- Joined: Fri Oct 24, 2008 3:43 pm
- Location: Saratoga Springs UT, USA
Call support
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.
- drporray
- New Member
- Posts: 13
- Joined: Mon Jun 15, 2009 10:14 am
- Location: Orem, Utah
-
- Member
- Posts: 228
- Joined: Fri Jan 19, 2007 1:13 pm
- Location: Provo, Utah, USA
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.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.
-
- Member
- Posts: 308
- Joined: Fri Jan 19, 2007 9:48 am
We need a public MLS known Bug list
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
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
-
- Member
- Posts: 83
- Joined: Sun Nov 01, 2009 9:15 pm
- Location: BC, Canada
-
- Member
- Posts: 228
- Joined: Fri Jan 19, 2007 1:13 pm
- Location: Provo, Utah, USA
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.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.
As I told them, if there ever is anything urgent, from now on it will be ignored.