Missionary Recommendation System

In the Stake section of the Missionary Recommend System, we show a missionary application that we are unable to open. Usually there is an underlined link to be able to view their application, but we cannot see that. Why can't we view it? If we can't view it, how do we remove it from the system?

Has the bishop completed the application and sent it to the stake?

The bishop doesn't even know who the member is. So to answer your question, no, the bishop has not completed the application. The application shows a different ward and stake as the submitting unit; however, the member is a part of our stake.

I wonder if their records got moved between wards during the process.

Each missionary recommendation has four unit designations: home, funding, submitting, and membership. It's possible the ward in your stake is designated as something other than "Submitting", because only the "Submitting" unit can click on the missionary name to complete the recommendation. The bishop (or clerks) can click on "Other Units" (to the right of the missionary's name) to see all of the unit designations and request changes; the stake cannot do this for them. The bishop (or clerks) can also contact Local Unit Support for additional technical support. Hope that helps!

So, a possibility is that the unit has been set as "funding" because that's where the parents live? However, I'd think the bishop would have been contacted at some point to get approval.

how we change our checklist on missionary online recommendation system but we have already submitted it?

We are unable to submit our Senior Missionary missionary recommendation.

The General Information section shows that it is incomplete and the "submit recommendation forms" button is greyed out. When I click on the General Information link it shows checkmarks next to every section:

Personal
Other People
Emergency Contact Name
Emergency Contact Address and Phone
Relatives Serving Missions

You may wish to try incognito/private mode. Church webpages have problems with cookie build-up and that's a quick test/workaround.