11 year old Deacon recommend error

[fletch1027]

We have an 11 year old that is turning 12 in a few months and this morning his father ordained him a Deacon, and our ward clerk recorded the ordination and everything looks good with that - he's now listed in LCR as a Deacon.

However, when I try and print off a limited use recommend so I can interview him today for a temple trip tomorrow, it errors saying that "This member is not old enough to receive a limited-use temple recommend.".

Any ideas, is it a glitch or is there some kind of back-end sync that hasn't happened yet? Thanks...

[mike.balzotti]

We get the same thing. I know there are others who have the same problem. Tried calling support, but they are closed for the Holiday.

[falcon771]

Just a guess, but other LCR changes are scheduled to take effect tomorrow. I wonder if the limited use recommends are in the same boat. Bishoprics in our stake are having the same issue. Try first thing in the morning.

[kpentz]

We have the same issue here in Colorado....

[fletch1027]

Thanks for the replies - glad it's not just me doing something wrong.

Hopefully it will be fixed by the AM!

[fletch1027]

UPDATE - I just tried again and it let me so it did seem to be some kind of sync lag or something they fixed on their end...

[kpentz]

Good news! Thanks for the update!

[scgallafent]

Limited use recommends were updated with the changes last year, so it's not something that is involved up in tomorrow's releases.

There is a lot of computer activity going on that started at about 4:00 AM Utah time on the 31st and is wrapping up this afternoon. Based on the monitoring messages in my inbox, it looks like we were generating about 15,000 change messages per minute for a while earlier today.

There is also a possibility that there is an "unexpected interaction" happening between systems that we didn't discover in testing.

[scgallafent]

Now that I've managed to dig a little further through my email, I see a message that there was a bug causing this and the issue was resolved at about 12:00 PM Utah time.

[johnshaw]

Steve, I have a bet going that it was a leap year issue in the code.... any chance you can confirm that