I just checked and my ward's meeting time is now correct in CDOL, but not yet on LUWS. Based on the nightly refresh procedure, I guess that means I can assume our LUWS will be correct by tomorrow morning.ryan jones wrote:LUWS does get the data from CDOL. I believe it is a nightly refresh.
Meeting Time changes aren't propogating
- aebrown
- Community Administrator
- Posts: 15153
- Joined: Tue Nov 27, 2007 8:48 pm
- Location: Draper, Utah
-
- Church Employee
- Posts: 2361
- Joined: Tue Jun 30, 2009 8:12 am
- Location: South Jordan, UT, USA
Alan_Brown wrote:I just checked and my ward's meeting time is now correct in CDOL, but not yet on LUWS. Based on the nightly refresh procedure, I guess that means I can assume our LUWS will be correct by tomorrow morning.
We have currently processed files received through Sunday afternoon (~ 5:30 MST). So most meeting times changes will be in now.
-
- Senior Member
- Posts: 3907
- Joined: Mon Sep 24, 2007 9:17 am
- Location: Cumming, GA, USA
So if I made the change two weeks ago Sunday (Dec 27th) and it still hasn't shown up in CDOL then I should probably try making a change again to get it to go through?ryan jones wrote:We have currently processed files received through Sunday afternoon (~ 5:30 MST). So most meeting times changes will be in now.
-
- Church Employee
- Posts: 2361
- Joined: Tue Jun 30, 2009 8:12 am
- Location: South Jordan, UT, USA
I would recommend that. Also if you would send me your unit number in a PM I will look to see if I can figure out why it didn't work the first time.eblood66 wrote:So if I made the change two weeks ago Sunday (Dec 27th) and it still hasn't shown up in CDOL then I should probably try making a change again to get it to go through?
-
- Church Employee
- Posts: 2361
- Joined: Tue Jun 30, 2009 8:12 am
- Location: South Jordan, UT, USA
It looks like you were on MLS version 3.1.2 when you changed your meeting time. You need to be on 3.1.3 when you change your meeting time for it to work. The process changed hopefully for the better :rolleyes: but with the timing of the 3.1.3 release there may be others in the same boat.ryan jones wrote:I would recommend that. Also if you would send me your unit number in a PM I will look to see if I can figure out why it didn't work the first time.
-
- Senior Member
- Posts: 3907
- Joined: Mon Sep 24, 2007 9:17 am
- Location: Cumming, GA, USA
That would explain why it didn't work for some us who did it early (using 3.1.2) and some who did it late (held up by CDOL processing) but did work for some in between.ryan jones wrote:It looks like you were on MLS version 3.1.2 when you changed your meeting time. You need to be on 3.1.3 when you change your meeting time for it to work. The process changed hopefully for the better :rolleyes: but with the timing of the 3.1.3 release there may be others in the same boat.
Once the CDOL processing is all caught up you may want to consider sending out an MLS message telling clerks to check their CDOL and/or LUWS times to make sure they updated since there probably are others who did it with 3.1.2 and who may not see this thread.
-
- Community Moderators
- Posts: 11460
- Joined: Mon Mar 17, 2008 10:27 pm
- Location: US
Bingo! You win the prize. You have correctly identified which of our units were able to successfully update their times and which units were not. I would never have thought of the version number as the discriminator.ryan jones wrote:It looks like you were on MLS version 3.1.2 when you changed your meeting time. You need to be on 3.1.3 when you change your meeting time for it to work. The process changed hopefully for the better :rolleyes: but with the timing of the 3.1.3 release there may be others in the same boat.
I do not second the motion for an MLS message, however, because conscientious clerks will try to change the meeting time once again without waiting for an MLS message.