Common Reasons Why a Minister Cannot Be Scheduled

This topic lists common reasons given in the Unscheduled Minister report and provides an explanation for why a minister cannot be scheduled.


 

Reason

Explanation

Team conflict. Current team and/or family ministry preferences setup cannot be scheduled due to the following conflicts): ...

The scheduler encountered a serious issue with your setup that is either preventing it from generating your entire schedule or from scheduling this minister.

Either a team or family preference setting is preventing this minister from being scheduled or preventing your entire schedule from being generated. Check the minister’s team preference settings and the family preference settings. For example, the minister may be a member of a Keep Apart team and a Keep Together team that are scheduled for the same event. To resolve the conflict, change one of the minister’s preference settings.

All ministers needed already scheduled at this point. Ministers needed are recalculated each time a schedule event slot is filled.

The number of ministers required was met. No additional ministers are currently needed to fill assignments.

Minister not available for the current scheduled event because this minister-member is already scheduled this weekend for a Sunday Obligation Mass.

The auto-scheduler did not schedule the minister for the event because he or she is already scheduled for a Sunday obligation event this weekend.

If you are attempting to schedule a minister for a Sunday obligation weekend event, and the minister is already scheduled for another Sunday obligation event during that same weekend, the auto-scheduler will only schedule the minister for one event held during that weekend. You can override the auto-scheduler by manually scheduling the minister (see Manually_Scheduling_Specific_Ministers_for_Events for details).

Minister not available for the current scheduled event because family members of this minister-member are already scheduled at another time this weekend for a Sunday Obligation Mass.

The auto-scheduler did not schedule the minister for the event because family members of this minister are already scheduled for a Sunday obligation event this weekend.

If you are attempting to schedule a minister for a Sunday obligation weekend event, and the minister's family members are already scheduled for a Sunday obligation event during that same weekend, the auto-scheduler will not schedule the minister. You can override the auto-scheduler by manually scheduling the minister (see Manually_Scheduling_Specific_Ministers_for_Events for details).

Unable to schedule minister on MUST keep together minister-team: name of team. One or more of the minister members are already scheduled this weekend for a Sunday Obligation Mass.

There are two probable reasons why the minister cannot be scheduled:

  • The scheduler partially fulfilled an event’s minister requirements by scheduling other ministers whose turn it is to serve. The scheduler cannot schedule this minister because he or she is on the named Keep Together team and that team has more ministers than the remaining number of ministers now required for the event.

  • The number of members on the Keep Together team exceeds the number of ministers needed for the event.

Unable to schedule keep-apart family member. Another member scheduled for "Family Ministry Preference" to which both belong.

The minister's family preference for this event is set to Keep Apart. Another family member is already scheduled for the event so to keep both members separate, the auto-scheduler cannot schedule this minister for the same event.

Minister is not available for special events.

The minister's member preferences indicate that he or she is not available for special events.

Minister is temporarily inactive.

The Temporarily Inactivate checkbox is selected in the minister's profile. This setting is applied either to the specific ministry or to all ministries.

Minister has valid exception dates.

The minister cannot be scheduled because Schedule Exception dates in the minister's preferences profile coincide with the date of the event.

Minister has valid exception dates associated with event.

The minister cannot be scheduled because Schedule Exception dates in the minister's preferences profile coincide with the date of the event.

Minister not available for the current scheduled event because this minister-member is already scheduled today at the same time.

The minister cannot be scheduled for this event because he or she is already scheduled for an event that occurs at the same time.

Minister not available for the current scheduled event based on the ministers willingness to serve.

The Willingness to serve selections in the minister's preferences profile make him or her unavailable to serve at the event.

Minister end date is before the current event date.

The minister's assignment end date occurs before the date of the event so the minister cannot be scheduled.

Minister start date is after the current event date.

The minister's assignment start date occurs after the date of the event so the minister cannot be scheduled.

Minister is a substitute.

The minister serves as a substitute only (the Sub Only? checkbox is selected in the minister's profile). The auto-scheduler does not automatically schedule a substitute minister. You can override the auto-scheduler by manually scheduling a substitute minister  (see Manually_Scheduling_Specific_Ministers_for_Events for details).

Unable to schedule minister on MUST keep together minister-team: name of team. Keep-together team has more ministers than what is needed.

The number of members on the Keep Together team exceeds the number of ministers needed for the event.

Unable to schedule minister on minister-team: name of team. All ministers needed already scheduled.

The minister requirement is already met. The minister cannot be scheduled.

Unable to schedule minister on MUST keep apart minister team:  name of team. Unable to schedule keep-apart minister-team minister. Another minister scheduled for name of team to which both belong.

The team preference is set to Keep Apart. Another team member is already scheduled for the event so to keep both members separate, the auto-scheduler cannot schedule this minister for the same event.

Minister belongs to a keep apart/keep together minister-team. Minister not scheduled to avoid conflict with keep apart/keep together minister-team.

The team preference is set to Keep Apart or Keep Together.  Either another team member is already scheduled for the event or another team member cannot serve at the event. To avoid a conflict with the team preference setting, the auto-scheduler cannot schedule this minister for the event.

 

Related Topics

 

<Back to top>