|
|
| Ligne 1 : |
Ligne 1 : |
| − | =Schedule Validation= | + | = Schedule Validation= |
| − | __NOTOC__
| |
| | | | |
| | Use the '''Review Messages''' window to manage warning and error messages that were generated the last time the schedule was built, validated, or rebuilt. | | Use the '''Review Messages''' window to manage warning and error messages that were generated the last time the schedule was built, validated, or rebuilt. |
| − |
| |
| − | The sections below cover:
| |
| − | * [[SchdlVldn#RvwVldnMsgWnd|Using the Review Messages window]].
| |
| − | * [[SchdlVldn#Warnings_List|The Warnings list]].
| |
| − | * [[SchdlVldn#Errors_List|The Errors list]].
| |
| | | | |
| | {{AnchorDiv|RvwVldnMsgWnd}} | | {{AnchorDiv|RvwVldnMsgWnd}} |
| Ligne 28 : |
Ligne 22 : |
| | |'''Close''' ''button'' | | |'''Close''' ''button'' |
| | |Discards all changes and closes the window. | | |Discards all changes and closes the window. |
| − | |}
| |
| − |
| |
| − | ==Warnings List==
| |
| − | {{NoteFormat|When Schedule building or validation generates the following warnings, the variable text shown here in braces { } is replaced with the actual value.|2}}
| |
| − |
| |
| − | {|class="no-border"
| |
| − | |-
| |
| − | |'''Warning[4]'''
| |
| − | |Too many days off have already been assigned for agent {A} on week with first day {B}.
| |
| − |
| |
| − | The user has assigned more days off to an agent in the specified week than are permitted by the agent's constraints. Contract weekend and/or day-off rules limit the number of days off allowed.
| |
| − | |-
| |
| − | |{{AnchorDiv|Warn8}}
| |
| − | '''Warning[8]'''
| |
| − | |No shifts match the constraints for agent {A} on day {B}; agent assigned a day off.
| |
| − |
| |
| − | Scheduler is forced to schedule a day off for this agent because no shifts match the agent's contract constraints for this day. If a shift is configured to be available on this day, then this warning signals a bad configuration of either the shift or an associated meal. Verify that the durations for the shift and meal are valid.
| |
| − | |-
| |
| − | |'''Warning[11]'''
| |
| − | |Adjacency constraints force a day off for agent {A} on day {B}.
| |
| − |
| |
| − | The minimum interval between two working days (as defined in Policies/Site Rules) cannot be satisfied. Therefore, Scheduler is forced to assign the agent a day off.
| |
| − | |-
| |
| − | |'''Warning[14]'''
| |
| − | |Meal {A} is in conflict with meal {B} for shift {C}.
| |
| − |
| |
| − | Two meals or shift splits conflict on a given shift. In this case, the first of these two meals or splits is removed from the shift.
| |
| − | |-
| |
| − | |'''Warning[16]'''
| |
| − | |The timestep constraint {A} is not satisfied for initial values of meal {B}.
| |
| − |
| |
| − | When you specify the starting timestep for a meal, you must satisfy other constraints. (For example, ensure that the meal does not overlap with other schedule items.)
| |
| − | |-
| |
| − | |'''Warning[22]'''
| |
| − | |Seniority of agent {A} is given as level {B}. This is greater than 100,000; therefore, the seniority level is set to 100,000.
| |
| − |
| |
| − | The specified agent has a seniority greater than 100,000. This should not occur in normal use of Workforce Management.
| |
| − | |-
| |
| − | |'''Warning[28]'''
| |
| − | |Forced day off for agent {A} on day {B} lowered weekly/monthly goals by {C} hours.
| |
| − |
| |
| − | Conflicting contract constraints will force the agent to have the day off. Usually, this is due to a combination of min/max/consecutive day-off and weekend day-off rules. It can also be caused by shift rejections.
| |
| − | |-
| |
| − | |{{AnchorDiv|Warn29}}
| |
| − | '''Warning[29]'''
| |
| − | |Cannot meet shift maximum occurrences constraint for agent {A} and shift {B}.
| |
| − |
| |
| − | Scheduler is unable to schedule a different shift, in violation of the constraint for maximum shift occurrence. This can occur if another shift is rejected or not available because of configuration constraints. It can also be caused by the start-time synchronicity constraint if alternate shifts do not allow the synchronicity constraint to be observed.
| |
| − | |-
| |
| − | |'''Warning[30]'''
| |
| − | |Cannot meet shift minimum occurrences constraint for agent {A} and shift {B}.
| |
| − |
| |
| − | Scheduler is unable to meet shift constraints with regard to minimum number of hours/days configured for the specified agent and shift. See [[SchdlVldn#Warn29|Warning[29]]], above.
| |
| − | |-
| |
| − | |'''Warning[31]'''
| |
| − | |Failed to satisfy constraint of type {A} for agent {B}.
| |
| − |
| |
| − | Scheduler was unable to assign the schedule items for the agent required by the specified constraint. Usually, this is due to a conflicting combination of constraints.
| |
| − | |-
| |
| − | |'''Warning[34]'''
| |
| − | |The start-step constraint {A} is not satisfied for initial values of shift {B}.
| |
| − |
| |
| − | Check that the shift start time is compatible with the timestep requested.
| |
| − | |-
| |
| − | |'''Warning[40]'''
| |
| − | |Agent {A} has made too many shift requests. {B} requests were granted; therefore, the satisfaction percentage has been decreased to {C}.
| |
| − |
| |
| − | The agent has made many shift preference requests. Only the specified number could be granted; therefore, the preference fulfillment ratio has been decreased by the indicated amount.
| |
| − | |-
| |
| − | |'''Warning[43]'''
| |
| − | |Planning period work constraint for the dates {A} - {B} for agent {C} cannot be satisfied.
| |
| − |
| |
| − | Because of conflicts in planning period constraint settings, workload constraints for this agent cannot be fulfilled for the specified days.
| |
| − | |-
| |
| − | |'''Warning[44]'''
| |
| − | |Agent {A} cannot be swapped because of either a nonstandard shift, a forced day off, or an infeasible day-off sequence within the swap period.
| |
| − |
| |
| − | The specified agent's schedule cannot be given to any other agent because it contains fixed elements that cannot be exchanged.
| |
| − | |-
| |
| − | |'''Warning[46]'''
| |
| − | |No activity was found for agent {A} on day {B} at timestep {C}; therefore, a forced break was assigned.
| |
| − |
| |
| − | None of this agent's assigned activities are available during the specified timestep(s). Therefore, Scheduler was forced to assign a break. This situation occurs when the agent's activities are all exclusive and could not be assigned without violating the minimum-duration-for-exclusive-activity constraint.
| |
| − | |-
| |
| − | |'''Warning[49]'''
| |
| − | |The paid exception or time off was removed on day {A} for agent {B} to find feasible shift.
| |
| − |
| |
| − | A part-day exception or time off that violates shift settings has been removed so that Scheduler can assign this agent a shift.
| |
| − | |-
| |
| − | |'''Warning[53]'''
| |
| − | |No shift of {A}'s contract can match preferences on day {B} (ignore).
| |
| − | |-
| |
| − | |'''Warning[54]'''
| |
| − | |Preference requirement on period ({A}..{B}) for agent {C} cannot be fulfilled, and is ignored.
| |
| − | |-
| |
| − | |'''Warning[55]'''
| |
| − | |Meal {A} does not fit in shift {B}. Shift can not be scheduled.
| |
| − | |-
| |
| − | |'''Warning[56]'''
| |
| − | |Time-window for day {A} of agent {B} reduced to [{C},{D}] to match activity open hours.
| |
| − | |-
| |
| − | |'''Warning[57]'''
| |
| − | |Break and meal sequence for [{A},{B}] duration of shift {C} was ignored as infeasible. Sequence: {D}
| |
| − | |-
| |
| − | |'''Warning[61]'''
| |
| − | |Planning period hours limit granted preferences to {A} for agent {B}. Decreasing quotas to {C}.
| |
| − | |-
| |
| − | |'''Warning[63]'''
| |
| − | |Single skill mode can not be used when task sequences are defined. Changing to multi-skill mode.
| |
| − | |-
| |
| − | |'''Warning[64]'''
| |
| − | |{A} constraint can not be satisfied for agent {B} starting at {C} and ending at {D}.
| |
| − |
| |
| − | The specified constraint for this agent cannot be satisfied for the specified date interval.
| |
| − | |-
| |
| − | |'''Warning[65]'''
| |
| − | |Some breaks could not be scheduled for agent {A} on day {B}.
| |
| − | |-
| |
| − | |'''Warning[66]'''
| |
| − | |Maximum shift item distance constraint could not be satisfied for agent {A} on day {B}.
| |
| − | |-
| |
| − | |'''Warning[67]'''
| |
| − | |Minimum shift item distance constraint could not be satisfied for agent {A}.
| |
| − | |-
| |
| − | |'''Warning[68]'''
| |
| − | |Shift items could not be scheduled at configured time intervals for agent {A} on day {B}.
| |
| − | |-
| |
| − | |'''Warning[69]'''
| |
| − | |Synchronization of the <<tt>xxx</tt>> shift item is ignored for agent {A} since synchronization of the contract shift item is enabled. Where <<tt>xxx</tt>> could be either team or shared transport.
| |
| − | |-
| |
| − | |'''Warning[70]'''
| |
| − | |Shift items could not be synchronized with other agents of the <<tt>xxx</tt>> for agent {A} on date {B}. Where <<tt>xxx</tt>> could be either team or shared transport.
| |
| − | |-
| |
| − | |'''Warning[71]'''
| |
| − | |Constraint of type {A} cannot be satisfied for <<tt>xxx</tt>> {D} at start date {B} and at end date {C}. Where <<tt>xxx</tt>> could be either team or shared transport.
| |
| − | |-
| |
| − | |'''Warning[77]'''
| |
| − | |Failed to satisfy constraint of type {B} for agent {A} on date {C}.
| |
| − | |-
| |
| − | |'''Warning[78]'''
| |
| − | |Constraint of type {A} cannot be satisfied for <<tt>xxx</tt>> {B} on date {C}. Where <<tt>xxx</tt>> could be either team or shared transport.
| |
| − | |-
| |
| − | |'''Warning[79]'''
| |
| − | |Constraint of type {A} cannot be satisfied for <<tt>xxx</tt>> {D} with contract {E} starting at {B} and ending at {C}. Where <<tt>xxx</tt>> could be either team or shared transport.
| |
| − | |-
| |
| − | |'''Warning[81]'''
| |
| − | |Contracts with different weekend start days were assigned for agent {A} during scheduling period {B} - {C}.
| |
| − | |-
| |
| − | |'''Warning[82]'''
| |
| − | |Contracts with different maximum consecutive work days were assigned for agent {A}. The value configured on the first day of scenario will be used.
| |
| − | |-
| |
| − | |'''Warning[90]'''
| |
| − | |The meeting {A} for agent {B} could not be scheduled.
| |
| − | |-
| |
| − | |'''Warning[91]'''
| |
| − | |The meeting {A} for agent {B} could not be scheduled on {C}.
| |
| − | |-
| |
| − | |'''Warning[92]'''
| |
| − | |The meeting {A} for agent {B} could not be scheduled during {C} - {D}.
| |
| − | |-
| |
| − | |'''Warning[93]'''
| |
| − | |Parameters of multi-site meeting {A} are invalid. The min/max group size cannot be satisfied with current number of agents and number of instances.
| |
| − | |-
| |
| − | |'''Warning[94]'''
| |
| − | |Parameters of the meeting {A} are invalid. The min/max group size cannot be satisfied with current number of agents and number of instances.
| |
| − | |-
| |
| − | |'''Warning[95]'''
| |
| − | |Multi-site meeting {A} was not scheduled. Could not find enough agents for one instance of the meeting.
| |
| − | |-
| |
| − | |'''Warning[96]'''
| |
| − | |The meeting {A} was not scheduled. Could not find enough agents for one instance of the meeting.
| |
| − | |-
| |
| − | |'''Warning[97]'''
| |
| − | |The multi-site meeting {A} could not be scheduled.
| |
| − | |-
| |
| − | |'''Warning[98]'''
| |
| − | |The meeting {A} could not be scheduled.
| |
| − | |-
| |
| − | |'''Warning[99]'''
| |
| − | |Parameters of multi-site meeting {A} on {B} are invalid. The min/max group size cannot be satisfied with current number of agents and number of instances.
| |
| − | |-
| |
| − | |'''Warning[100]'''
| |
| − | |Parameters of the meeting {A} on {B} are invalid. The min/max group size cannot be satisfied with current number of agents and number of instances.
| |
| − | |-
| |
| − | |'''Warning[101]'''
| |
| − | |Parameters of multi-site meeting {A} during {B} - {C} are invalid. The min/max group size cannot be satisfied with current number of agents and number of instances.
| |
| − | |-
| |
| − | |'''Warning[102]'''
| |
| − | |Parameters of the meeting {A} during {B} - {C} are invalid. The min/max group size cannot be satisfied with current number of agents and number of instances.
| |
| − | |-
| |
| − | |'''Warning[103]'''
| |
| − | |Multi-site meeting {A} on {B} was not scheduled. Could not find enough agents for one instance of the meeting.
| |
| − | |-
| |
| − | |'''Warning[104]'''
| |
| − | |The meeting {A} on {B} was not scheduled. Could not find enough agents for one instance of the meeting.
| |
| − | |-
| |
| − | |'''Warning[105]'''
| |
| − | |Multi-site meeting {A} on {B} was not scheduled. Could not find enough agents for one instance of the meeting.
| |
| − | |-
| |
| − | |'''Warning[106]'''
| |
| − | |The meeting {A} on {B} was not scheduled. Could not find enough agents for one instance of the meeting.
| |
| − | |-
| |
| − | |'''Warning[107]'''
| |
| − | |The multi-site meeting {A} could not be scheduled on {B}.
| |
| − | |-
| |
| − | |'''Warning[108]'''
| |
| − | |The meeting {A} could not be scheduled on {B}.
| |
| − | |-
| |
| − | |'''Warning[109]'''
| |
| − | |The multi-site meeting {A} could not be scheduled during {B} - {C}.
| |
| − | |-
| |
| − | |'''Warning[110]'''
| |
| − | |The meeting {A} could not be scheduled during {B} - {C}.
| |
| − | |-
| |
| − | |'''Warning[111]'''
| |
| − | |{B} out of {C} instances of multi-site meeting {A} could not be scheduled.
| |
| − | |-
| |
| − | |'''Warning[112]'''
| |
| − | |{B} out of {C} instances of the meeting {A} could not be scheduled.
| |
| − | |-
| |
| − | |'''Warning[1000]'''
| |
| − | |Calendar item containing invalid shift ID={A} assigned to agent '{B}' on day {C}.
| |
| − | |-
| |
| − | |'''Warning[1001]'''
| |
| − | |Exception will be ignored for overnight shift of day {A} for agent '{B}'. Strict work time can not accommodate partially covered exception.
| |
| − | |-
| |
| − | |'''Warning[1002]'''
| |
| − | |Schedule start date weekday is not the same as long period start day. Moving long period back {A} days.
| |
| − | |-
| |
| − | |'''Warning[1003]'''
| |
| − | |Task sequence '{A}' was removed as it contains activity set '{B}' with no activities or assigned activities are not present in schedule scenario.
| |
| − | |-
| |
| − | |'''Warning[1004]'''
| |
| − | |Null element ignored in break meal list of shift '{A}'
| |
| − | |-
| |
| − | |'''Warning[1005]'''
| |
| − | |Both break and meal are not null element in break meal list of shift '{A}'
| |
| − | |-
| |
| − | |'''Warning[1006]'''
| |
| − | |Shift '{A}' task sequence ID={B} was not found.
| |
| − | |-
| |
| − | |'''Warning[1007]'''
| |
| − | |Agent '{A}' has no assigned contract. Agent will not be scheduled.
| |
| − | |-
| |
| − | |'''Warning[1008]'''
| |
| − | |Contract ID={A} assigned to agent '{A}' is unknown at site '{B}'.
| |
| − | |-
| |
| − | |'''Warning[1009]'''
| |
| − | |Agent '{A}' has accrual rule ID={B} that is not known to WFM Server.
| |
| − | |-
| |
| − | |'''Warning[1010]'''
| |
| − | |The team ID={A} of agent '{B}' does not exist at site '{C}'.
| |
| − | |-
| |
| − | |'''Warning[1012]'''
| |
| − | |Removed activity set '{A}' with no activities. Activities are either not present in schedule scenario or not configured properly.
| |
| − | |-
| |
| − | |'''Warning[1013]'''
| |
| − | |Removed task sequence '{A}' ID={B} since it contains invalid activity sets. Check prior warnings for activity set configuration problems.
| |
| − | |-
| |
| − | |'''Warning[1014]'''
| |
| − | |Removed agent '{A}' with no activities. Activities are either not assigned to agent, missing in schedule scenario or not configured properly.
| |
| − | |-
| |
| − | |'''Warning[1015]'''
| |
| − | |Minimum shift '{A}'s' paid duration is not covered by combine list. Minimum shift paid time changed to {B} hours {C} minutes.
| |
| − | |-
| |
| − | |'''Warning[1016]'''
| |
| − | |Task sequence ID={A} was removed from shift '{B}'. Task sequence may be misconfigured or contain not available activity set.
| |
| − | |-
| |
| − | |'''Warning[1017]'''
| |
| − | |Shift '{A}' was removed since it has no assigned mandatory task sequences.
| |
| − | |-
| |
| − | |'''Warning[1018]'''
| |
| − | |One or more shifts assigned to contract '{A}' could not be used due to configuration problems.
| |
| − |
| |
| − | Not all shifts that were assigned to contract could be used for scheduling. This warning usually is issued after more detailed shift configuration warnings.
| |
| − | |-
| |
| − | |'''Warning[1019]'''
| |
| − | |Agent '{A}' will not be scheduled. Scenario activities can not be used in any one of task sequences of contract shifts.
| |
| − |
| |
| − | Schedule scenario does not contain activities that are required to schedule shifts with mandatory task sequences.
| |
| − | |-
| |
| − | |'''Warning[1020]'''
| |
| − | |Activity sets will be used for scheduling even though task sequences exist in the site.
| |
| − |
| |
| − | Task sequences exist in the database but are not assigned to the shifts.
| |
| − | |-
| |
| − | |{{AnchorDiv|Warn1021}}
| |
| − | '''Warning[1021]'''
| |
| − | |Removed contract '{A}'. Shifts assigned to this contract are not configured properly.
| |
| − |
| |
| − | Contract has no useable shifts, and therefore the contract is removed from scheduling. Shift configuration problems are described in other warnings.
| |
| − | |-
| |
| − | |'''Warning[1022]'''
| |
| − | |Removed agent '{A}' with a contract that was not correctly configured.
| |
| − |
| |
| − | Contract that was assigned to agent cannot be used. This warning usually follows [[SchdlVldn#Warn1021|warning 1021]].
| |
| − | |-
| |
| − | |'''Warning[1023]'''
| |
| − | |Schedule of agent '{A}' was not re-optimized.
| |
| − |
| |
| − | During Intra-Day scheduling, the agent's schedule for a particular day could not be modified because the current configuration prevents scheduling of a valid shift on that day.
| |
| − | |-
| |
| − | |'''Warning[1024]'''
| |
| − | |Weekly rotating paid hours {A}:{B} - {A}:{B} for agent '{C}' on week {C} - {C} are not compatible with contract on this week.
| |
| − | |-
| |
| − | |'''Warning[1025]'''
| |
| − | |Calendar item for agent '{A}' on the last day of schedule overlaps the shift on the next day.
| |
| − | |-
| |
| − | |'''Warning[1026]'''
| |
| − | |Removed profile '{A}' with no activities. Activities are either not assigned to profile, missing in schedule scenario, or not configured properly.
| |
| − | |-
| |
| − | |'''Warning[1027]'''
| |
| − | |Removed profile '{A}' with the incorrectly configured contract.
| |
| − | |-
| |
| − | |'''Warning[1028]'''
| |
| − | |Profile '{A}' will not be scheduled. Scenario activities cannot be used in any one of task sequences of contract shifts.
| |
| − | |-
| |
| − | |'''Warning[1029]'''
| |
| − | |Contract ID={A} assigned to profile '{B}' is unknown at site '{C}'.
| |
| − | |-
| |
| − | |'''Warning[1030]'''
| |
| − | |The understaffing limit could not be reached during profile optimization scheduling.
| |
| − | |-
| |
| − | |'''Warning[1031]'''
| |
| − | |Meeting '{A}' cannot be scheduled after time zone conversion.
| |
| − | |-
| |
| − | |'''Warning[1032]'''
| |
| − | |Meeting '{A}' time zone cannot be determined.
| |
| − | |-
| |
| − | |'''Warning[1033]'''
| |
| − | |Meeting '{A}' cannot be scheduled at site '{B}' due to inaccessible exception type.
| |
| − | |-
| |
| − | |'''Warning[1034]'''
| |
| − | |No activities are available for agent '{A}' on '{B}'. Agent assigned a day off.
| |
| − | |-
| |
| − | |'''Warning[1035]'''
| |
| − | |No contract is assigned for agent '{A}' on '{B}'. Agent assigned a day off.
| |
| − | |-
| |
| − | |'''Warning[1036]'''
| |
| − | |Meeting '{A}' start or end date is not specified. Cannot schedule this meeting.
| |
| − | |}
| |
| − |
| |
| − | ==Errors List==
| |
| − | {{NoteFormat|When Schedule building or validation generates the following errors, the variable text shown here in braces { } is replaced with the actual value.|2}}
| |
| − |
| |
| − | {|class="no-border"
| |
| − | |-
| |
| − | |'''Error[4]'''
| |
| − | |Schedule build was canceled by user.
| |
| − | |-
| |
| − | |'''Error[6]'''
| |
| − | |Wrong scheduling start date {A} and/or end date {B}.
| |
| − | |-
| |
| − | |'''Error[8]'''
| |
| − | |0 is not a valid value for minimal daily workload in contract {A}.
| |
| − | |-
| |
| − | |'''Error[9]'''
| |
| − | |The minimum/maximum constraints for contract {A} make it impossible to schedule.
| |
| − | |-
| |
| − | |'''Error[10]'''
| |
| − | |The minimum weekly workload cannot be reached for contract {A}.
| |
| − | |-
| |
| − | |'''Error[11]'''
| |
| − | |The minimum planning period workload cannot be reached for contract {A}.
| |
| − | |-
| |
| − | |'''Error[12]'''
| |
| − | |The day {A} that was given is outside the planning period.
| |
| − | |-
| |
| − | |'''Error[13]'''
| |
| − | |On day {A}, activity {B} has not been declared.
| |
| − | |-
| |
| − | |'''Error[15]'''
| |
| − | |On day {A}, the charge specification for activity {B} has the wrong length.
| |
| − | |-
| |
| − | |'''Error[16]'''
| |
| − | |The code for contract {A} given for the agent {B} is not valid.
| |
| − | |-
| |
| − | |'''Error[21]'''
| |
| − | |The code number {A} is not valid to designate an agent.
| |
| − | |-
| |
| − | |'''Error[28]'''
| |
| − | |Wrong shift index: {A}
| |
| − | |-
| |
| − | |'''Error[29]'''
| |
| − | |Wrong meal index: {A}
| |
| − | |-
| |
| − | |'''Error[32]'''
| |
| − | |The day-of-week indexed by number {A} is not valid. See definition of shift {B}.
| |
| − | |-
| |
| − | |'''Error[34]'''
| |
| − | |Too many activities configured: {A} is the maximum number of activities. Configured {B}.
| |
| − | |-
| |
| − | |'''Error[36]'''
| |
| − | |Impossible to overwrite shift for agent {A} on day {B}: unpaid times and work length not compatible.
| |
| − | |-
| |
| − | |'''Error[38]'''
| |
| − | |Activity hours start time {A}, end time {B}, for activity {C} not compatible with scheduled hours.
| |
| − | |-
| |
| − | |'''Error[40]'''
| |
| − | |Contradictory requirements for agent {A} on day {B}: agent should be both present and off.
| |
| − | |-
| |
| − | |'''Error[43]'''
| |
| − | |Too many shifts: the maximum number is {A}, but more than {B} were requested.
| |
| − | |-
| |
| − | |'''Error[45]'''
| |
| − | |Wrong preference time window for agent {C}: timestep {A} < timestep {B}.
| |
| − | |-
| |
| − | |'''Error[46]'''
| |
| − | |Rescheduling data of agent {A} on day {B} is inconsistent with the current meal definition. Restore initial settings before rescheduling.
| |
| − | |-
| |
| − | |'''Error[47]'''
| |
| − | |The list of time windows for a meeting between time {A} and time {B} is incorrect.
| |
| − | |-
| |
| − | |'''Error[50]'''
| |
| − | |Weekly work constraint for agent {A} has invalid dates {B} and {C}.
| |
| − | |-
| |
| − | |'''Error[51]'''
| |
| − | |Rescheduling data of agent {A} on day {B} is inconsistent with current shift definition. Do not change it before rescheduling.
| |
| − | |-
| |
| − | |'''Error[52]'''
| |
| − | |Wrong break index: {A}
| |
| − | |-
| |
| − | |'''Error[53]'''
| |
| − | |Wrong activity index: {A}
| |
| − | |-
| |
| − | |'''Error[54]'''
| |
| − | |Wrong task sequence index: {A}
| |
| − | |-
| |
| − | |'''Error[55]'''
| |
| − | |Activity {A} already belongs to activity set {B} (hence cannot be included in activity set {C})
| |
| − | |-
| |
| − | |'''Error[56]'''
| |
| − | |Invalid break sequence({A}): all alternatives of the combine list must share the same unpaid length
| |
| − | |-
| |
| − | |'''Error[58]'''
| |
| − | |Invalid task sequence({A}): mismatching start/end anchors
| |
| − | |-
| |
| − | |'''Error[59]'''
| |
| − | |Exclusive activities and task sequences cannot coexist
| |
| − | |-
| |
| − | |'''Error[60]'''
| |
| − | |No agent has been defined: solve aborted.
| |
| − | |-
| |
| − | |'''Error[62]'''
| |
| − | |Shortest shift item sequence for shift {A} has minimum duration of {B}. Sequence covering minimum shift duration is required.
| |
| − | |-
| |
| − | |'''Error[63]'''
| |
| − | |Shift {A} item sequence for longer shift contains less unpaid time ({B} minutes) than shorter sequence.
| |
| − | |-
| |
| − | |'''Error[64]'''
| |
| − | |The item sequence number added is incorrect. You specified {A} when {B} was expected.
| |
| − | |-
| |
| − | |'''Error[65]'''
| |
| − | |Schedule build was canceled due to scheduling error from another site of the scenario.
| |
| − | |-
| |
| − | |'''Error[66]'''
| |
| − | |Internal scheduling engine error.
| |
| − | |-
| |
| − | |'''Error[1000]'''
| |
| − | |Failed to load schedule scenario. Scenario ID={A}
| |
| − | |-
| |
| − | |'''Error[1001]'''
| |
| − | |Loaded schedule scenario does not contain required site. Scenario ID={A}, site ID={B}.
| |
| − | |-
| |
| − | |'''Error[1002]'''
| |
| − | |Specified schedule interval is {A} days. At least one week is required.
| |
| − | |-
| |
| − | |'''Error[1003]'''
| |
| − | |Specified schedule interval is {A} days long. Schedule period can not be longer than 6 weeks.
| |
| − | |-
| |
| − | |'''Error[1004]'''
| |
| − | |Specified schedule interval is {A} days long. Schedule period must contain exact number of weeks.
| |
| − | |-
| |
| − | |'''Error[1005]'''
| |
| − | |Invalid long period type={A} detected (more than 6 weeks or less than 0) for site '{B}'.
| |
| − | |-
| |
| − | |'''Error[1006]'''
| |
| − | |WFM Server returned 0 sites.
| |
| − | |-
| |
| − | |'''Error[1007]'''
| |
| − | |Site to be scheduled was not found in database. Site ID={A}.
| |
| − | |-
| |
| − | |'''Error[1008]'''
| |
| − | |Activities not found in the database for site '{B}'.
| |
| − | |-
| |
| − | |'''Error[1009]'''
| |
| − | |Activity '{B}' belongs to unknown activity set. Set ID={A}.
| |
| − | |-
| |
| − | |'''Error[1011]'''
| |
| − | |Task anchor value {A} is incorrect for sequence '{B}' task index={A}.
| |
| − | |-
| |
| − | |'''Error[1012]'''
| |
| − | |Unknown break ID={A} assigned to shift '{B}'.
| |
| − | |-
| |
| − | |'''Error[1013]'''
| |
| − | |Unknown meal ID={A} assigned to shift '{B}'.
| |
| − | |-
| |
| − | |'''Error[1014]'''
| |
| − | |Meal ID={A} is in combine list but not assigned to shift '{B}'.
| |
| − | |-
| |
| − | |'''Error[1015]'''
| |
| − | |Break ID={A} is in combine list but not assigned to shift '{B}'.
| |
| − | |-
| |
| − | |'''Error[1016]'''
| |
| − | |Can not create schedule. Schedule scenario or configuration is not valid.
| |
| − | |-
| |
| − | |'''Error[1017]'''
| |
| − | |Synchronize work start threshold value {A} is out of range [-1, 6]—for site '{B}'.
| |
| − | |-
| |
| − | |'''Error[1018]'''
| |
| − | |Can not schedule task sequences in single skill scheduling mode. Use multi-skill scheduling instead.
| |
| − | |-
| |
| − | |'''Error[1020]'''
| |
| − | |Unknown calendar item exception type ID={A} assigned to agent '{B}' on day {C}.
| |
| − | |-
| |
| − | |'''Error[1021]'''
| |
| − | |No activities configured for scheduling. Check schedule scenario and configuration.
| |
| − | |-
| |
| − | |'''Error[1022]'''
| |
| − | |No contracts configured for scheduling. Check schedule scenario and configuration.
| |
| − | |-
| |
| − | |'''Error[1023]'''
| |
| − | |No shifts configured for scheduling. Check schedule scenario and configuration.
| |
| − | |-
| |
| − | |'''Error[1024]'''
| |
| − | |No agents configured for scheduling. Check schedule scenario and configuration.
| |
| − | |-
| |
| − | |'''Error[1025]'''
| |
| − | |Long period start date is not defined for site '{A}'.
| |
| − | |-
| |
| − | |'''Error[1035]'''
| |
| − | |No daily agent schedules are available for schedule re-optimization.
| |
| − | |-
| |
| − | |'''Error[1036]'''
| |
| − | |No profiles configured for scheduling for site '{A}'. Check schedule scenario and configuration.
| |
| − | |-
| |
| − | |'''Error[1037]'''
| |
| − | |Estimated number of profile agents is zero.
| |
| − | |-
| |
| − | |'''Error[1038]'''
| |
| − | |Time zone with specified ID={A} not found.
| |
| − | |-
| |
| − | |'''Error[1039]'''
| |
| − | |Sites from different Business Units specified in the scheduling request.
| |
| − | |-
| |
| − | |'''Error[1040]'''
| |
| − | |Internal error. Configuration of some of sites in the schedule request could not be loaded.
| |
| − | |-
| |
| − | |'''Error[1041]'''
| |
| − | |Internal error. Some of sites in the schedule request do not exist in the schedule scenario.
| |
| − | |-
| |
| − | |'''Error[1066]'''
| |
| − | |Internal error.
| |
| − | |-
| |
| − | |'''Error[1068]'''
| |
| − | |WFM Builder failed to save schedule.
| |
| − | |-
| |
| − | |'''Error[1069]'''
| |
| − | |WFM Server communication problem: {A}.
| |
| − | |-
| |
| − | |'''Error[1070]'''
| |
| − | |WFM Server communication problem.
| |
| − | |-
| |
| − | |'''Error[1071]'''
| |
| − | |Configuration Server communication problem: {A}.
| |
| − | |-
| |
| − | |'''Error[1072]'''
| |
| − | |More than one WFM Server specified in Builder connections.
| |
| − | |-
| |
| − | |'''Error[1073]'''
| |
| − | |WFM Server not specified in application connections.
| |
| − | |-
| |
| − | |'''Error[1074]'''
| |
| − | |Failed to retrieve WFM Server '{A}' information.
| |
| − | |-
| |
| − | |'''Error[1075]'''
| |
| − | |Failed to retrieve Business Unit ID={A}.
| |
| | |} | | |} |
| | | | |
| | [[Category:V:WM:DRAFT]] | | [[Category:V:WM:DRAFT]] |
