Troubleshooting Appointment and Schedule Proposals
When you use Schedule Proposals and Appointment Proposals, Error and Warning messages sometimes appear. The Jobs that trigger Error messages are excluded from Schedule Proposal results. When Warning messages are triggered, the related Jobs are filtered out of the payload before data is sent to the optimization engine.
|
Message
|
Causes and Solutions
|
|---|---|
|
The following Jobs are excluded from this Schedule Proposal because they were previously dispatched. [WO-00000001]
|
Triggered when Propose Schedule is invoked for Jobs that have previously scheduled Appointments. This error occurs only in cases where Optimized Rescheduling is not enabled in the selected Optimization Setting record.
|
|
Data validation error (Error code: 517). Address and geocode of the "Default Location" field cannot both be empty for Resource(s): "Simon".
|
Check that the Default Location field of the reported Resource record is not empty, and that the Job record has valid data specified in the Address field.
|
|
Could not schedule Job(s): WO-000000014 (Error code: 402). There is not enough overlap between the access hours of job and its preferred start/end time.
|
Check that the Preferred Start Time and Preferred End Time values for the relevant Job have valid values that fall within the schedule horizon, and that valid Shift information is defined.
|
|
Could not schedule Job(s): WO-00000030 (Error code: 112). Scheduling job would have exceeded the maximum travel distance.
|
The Job location is too far away from the Resource location. Check that the Job location is within reasonable travel distance, or increase the Maximum Travel Distance Per Resource Per Day value in the relevant Optimization Setting record.
|
|
Data validation error (Error code: 502). The value of the field "Estimated Service Duration" cannot be zero or negative for Job(s): WO-000000014.
|
Check that the Estimated Service Duration value in the relevant Job record is greater than zero and is not negative.
|
|
Could not initiate Schedule Proposals (Error code: 505). No active or valid resources specified.
|
All Resources in the currently selected Scheduler Resource List are inactive, which means no valid information can be sent to the optimization engine.
|
|
Data validation error (Error code: 512). The value of Field "workingHours" cannot be greater than 1 day for Resource(s): "Simon".
|
If no Shift information is configured in Resource, User Preference, or System Settings records, a single duration from start to end dates that spans multiple days is used as Working Hours for the relevant Resource. To avoid this error, configure Shift information.
|
|
Warning for Job(s): WO-000000014 (Error code: 107). The resource is scheduled to be on location after the access hour of job.
|
Check that Shifts configured for Resources fall within the same time zones that are configured for the relevant Jobs, or that two currently configured Shifts have adequate overlap to fulfill required Job durations.
|
|
The following events are excluded from Schedule Proposals as they are not within resource working hours (Error code: 411): "Meeting"
|
Existing Event or Appointment records fall within nonworking hours for the relevant Resources, and are unmodified during optimization.
|
|
Data validation error (Error code: 536). The preferred start value cannot be later than the preferred end value for Job(s): WO-000000014.
|
The Preferred End Time value is earlier than the Preferred Start Time value for the relevant Job.
|
|
Data validation error (Error code: 537). The level value of job requirement or qualification cannot be less than 1 for Job(s): [svmx_job](WO-03691413 | 2ba2b1c1-546c-4bea-bbf0-5d99ef1a121b).
|
The Minimum Level value in the related Job Requirement record or the Level field value in the related Qualification record are 0 or null.
|
|
Could not schedule Job(s): WO-000000014 (Error code: 101). No eligible resources possess all skills or hard constraint is violated.
|
None of the Resources in the currently selected Resource List meet required skill levels, or hard constraints cannot be fulfilled, for example, mandatory Resources are not included in the payload.
|
 |
When multiple errors of the same type occur, they are aggregated and reported together. For example, when two 536 errors occur, the error message is Data validation error (Error code: 536). The preferred start value cannot be later than the preferred end value for Job(s): WO-00010753, WO-00010763. In cases where three errors of the same type occur, three record names appear, and when more than three errors of the same type occur, the first three record names appear followed by an ellipsis (…) to indicate additional errors.
|
For more information: