|
Message
|
What It Means
|
Resolution
|
|---|---|---|
|
Primary territory for this work order could not be calculated.
|
This error might occur because of one of the following reasons:
• Territory matching rules were not defined.
• This work order did not match any territory match rules.
• A matching territory rule did not yield any territories for this work order.
|
• Turn SET049 to False and define the territory manually.
• Define the correct territory match rule.
|
|
Skip this update for ForceFix Call. Job is already Fixed, so any changes to the fields affecting scheduling should not be performed.
|
The work order might be already fixed.
|
No resolution is needed.
|
|
Skip this update for External work order is already fixed.
|
The work order might be already fixed.
|
No resolution is needed.
|
|
Job is scheduled to be part of dependency group, first cancel the dependency manually and try again.
|
The work order cannot be deleted because it is part of a dependency group.
|
You can remove the dependency rule or update it so that it is picked up for scheduling.
|
|
As both PST and PET are out of the Horizon, skipping this WO from scheduling.
|
Specify feasible PST and PET.
|
|
|
As PST is out of the Horizon and PET is null, skipping this WO from scheduling.
|
PST is outside the dispatch horizon and PET is blank.
|
|
|
As PST is NULL and PET is out of Horizon, skipping this WO from scheduling.
|
||
|
Either work Order (complete address or zip/country) or Service Duration is null, or QTL status is Disallow.
|
Ensure that the work order has correct information.
|
|
|
If Server is down: Return Code:500 | Return Msg: Internal Server Error
|
The server might be down, or the request is queued up.
|
Contact the Operations Support team.
|
|
Hard Constraint violated: 104, The node cannot be injected. The node seems to carry hard constraints which cannot be satisfied.
|
Skill or the mandatory or excluded technicians rule is violated.
|
Update technician records with required skills.
|
|
Skill Hard Constraint violated: Skill hard constraint is violated.
|
Cannot find a technician who has the required skill for the work order.
|
Update technician records with required skills.
|
|
Working hours exceeded- Total working hours of the technician exceeded constraint is violated.
|
Validate the technician's working hours.
|
|
|
Work Order does not have valid Operation Type.
|
The Scheduling Change Token field in the work order might be deleted.
|
Ensure that the appropriate scheduling change token is available in the work order.
|
|
No work orders with valid address or data are available for optimized dispatch.
|
There are no qualified work orders for the job run.
|
Ensure that the work order has all the required and correct data.
|
|
No technicians with valid address or data are available for optimized dispatch.
|
Technicians with correct information are not available.
|
Update technician records with the required information.
|
|
Another event already has taken this slot, the resources workingHours are not matching to the event or the event cannot be reached in time.
|
The event cannot be scheduled because of one of the following reasons:
• The technician is already occupied with another event.
• The event’s access hours do not match the technician’s working hours.
• The event is not reachable within access hours.
• Work order assigned within the dispatch threshold.
• The work order is overlapping with another manually assigned work order or technician event.
• The work order is assigned outside the technician’s working hours.
• The work order is not reachable. The driving time to reach the work order is more than the time available with the technician. For example, you have manually assigned a work order from 10:00 AM-11:00 AM. Now you manually assign another work order to the same technician at 11:15 AM, which has a drive time of 30 minutes. In this case, the second work order is rejected because the time available with the technician is not sufficient to reach the work order.
• The work order is assigned at the beginning of the working hours, but the “Before the shift begins, technicians should drive on their own time for up to (Minutes)” parameter is not set in the Dispatch Process. Or, the driving time to reach the work order is greater than the value set in the parameter.
• The work order is assigned at the end of the working hours, but the “After the shift ends, technicians should drive on their own time for up to (Minutes)” parameter is not set in the Dispatch Process.
|
|
|
Technician not found in the job for the force fix work order.
|
The technician assigned during the manual scheduling is not part of the RTO job.
|
|
|
Work Order does not have valid Latitude-Longitude.
|
The latitude-longitude information specified in the work order is not valid.
|
Ensure that the work order has valid longitude-latitude information.
|
|
Resource does not have valid Operation Type.
|
The operation type of the resource is null or invalid in the request sent to the server.
|
|
|
Technician Event does not have valid Operation Type.
|
The operation type of the event is null or invalid in the request sent to the server.
|
|
|
Geocoding error
|
Failed to geocode the element address.
|
|
|
The node cannot be injected. Most likely no routes are available that are not finalized.
|
There are no schedulable days available for the technician where the work order can be placed, or all the days have been utilized for scheduling.
|
|
|
Element removed from job post resource update. Element access hours not inside resource business hours.
|
The work order’s access hours are outside the technician’s working hours.
|
|
|
PST is greater than PET or PST equals PET. Correct the data to proceed further.
|
The PST and PET values specified in the work order are the same, or the PST is greater than the PET.
|
Ensure that the work order has valid PST and PET values.
|
|
Return Code:503 | Return Msg:Service Temporarily Unavailable
|
The server is temporarily not able to process the request.
|
Contact the administrator.
|
|
Return Code:504 | Return Msg:Gateway Time-out
|
The server is temporarily not able to process the request.
|
|
|
Work Order not found at ECO System to update.
|
The work order is not present on the server and the update request is rejected.
|
Clear the following fields and save the work order:
• OptiMax Status
• Dispatch Process
• Scheduling Status
• Scheduling Change Token
|
|
Work Order found at ECO System, but it is not Optimizable. Please remove and add again.
|
The work order is already marked as Dispatched on the Server. Further updates are not considered.
|
|
|
Failed to resolve address using SLR-GeoCoding Service.
|
The SLR-GeoCoding service failed to resolve the latitude and longitude from the address provided.
|
|
|
This work order has more than one events so Locked By DC field cannot be unchecked.
|
Dispatcher tried to uncheck the Locked By DC field for a multiple assignment work order.
|
|
|
Work Order does not have valid service duration.
|
Service duration has not been populated for the work order. Or, the service duration specified in the work order is not valid.
|
Ensure that valid service duration is populated in the work order.
|
|
Work Order does not have valid Priority.
|
Dispatch priority is not populated for the work order.
|
Ensure that the work order has valid dispatch priority.
|
|
Access hour cannot be greater than 24 hours.
|
Work order has invalid access hours.
|
Ensure that the work order has valid access hours.
|
|
Event duration cannot be greater than 24 hours.
|
The work order has an invalid event duration.
|
Ensure that the work order has a valid event duration.
|
|
Work order visit duration cannot be greater than 24 hours.
|
The work order has an invalid visit duration.
|
Ensure that the work order has a valid visit duration.
|
|
Event access hour merge with technician working hours failed.
|
The work order access hours do not match the technician's business hours.
|
Ensure that there is no conflict between work order access hours and technician business hours.
|
|
Master node of this related node has been removed.
|
The work order is part of a dependency group and the primary work order is no longer available.
|
Resolve the dependency group conflict.
|
|
The pillar was added even though a violation was created. The associated route was inactivated.
|
The work order is part of an unoptimizable route.
|
|
|
A pillar cannot be injected within the lockdown time or in the past.
|
The work order cannot be scheduled within the dispatch threshold time window or the work order is in the past.
|
|
|
Route which the element is part of has been marked as non-optimizable.
|
The work order is non-optimizable as it is part of an unoptimizable route. This work order might not be the reason for the route inactivation.
|
|
|
Element is UnReachable. Route has been marked as non-optimizable.
|
The work order is non-optimizable as it is part of an unoptimizable route. This work order might be the reason for route inactivation.
|
Correcting the previous action might make this route active.
|
|
Technician Event (PillarEventNode) found at ECO system but not optimizable. Please remove and add again.
|
The technician event without location is currently within the dispatched threshold time window, and hence non-optimizable.
|
Remove this event and add it again after the scheduled date and time of the event have passed. It might be updated and scheduled after the start of the next business hour.
|
|
Technician Event (PillarEventNode) not found at ECO system to update.
|
An update operation has been requested on the technician event without location. But it is only possible if the event is already present. In this case, the element is not found.
|
Add the technician event instead of updating it.
|
|
Failed to update technician event (PillarTimeWindowGeoNode).
|
Failed to complete the requested updated operation on technician event or manual work order with location information.
|
Verify the server logs to find the reason if no other specific message is available.
|
|
Technician Event (PillarTimeWindowGeoNode) found at ECO System, but not optimizable. Please remove and add again.
|
The work order is not optimizable.
|
|
|
Technician Event (PillarTimeWindowGeoNode) not found at ECO System to update.
|
An update operation has been requested on the technician event or the manual work order with a location. But it is only possible if the event is already present.
|
Add the technician event or the manual work order instead of updating it.
|
|
Technician event (PillarTimeWindowGeoNode) already exists at ECO System. Please update or remove and add again.
|
An add operation is requested for the technician event or the manual work order with the location. But the event is already present.
|
Update the work order, or remove and add the work order again.
|
|
Related Work Order (TimeWindowGeoNode) Id passed is empty.
|
There is a work order which is now converted to a fixed event. So, the created event should mention the corresponding work order ID as the related ID. The work order will be replaced with the fixed event.
|
|
|
Related Work Order (TimeWindowGeoNode) Id passed is incorrect.
|
The related work order ID is passed as part of the request to convert an existing work order to a technician event. But, the ID is not of the work order type already present. It might have been an event already, so the request is rejected.
|
|
|
Related Work Order (TimeWindowGeoNode) found at ECO System, but not optimizable. Please remove and add again.
|
The technician event or manual work order with location is now within the dispatch threshold time window and no longer optimizable.
|
Remove technician event or manual work order after the scheduled date and time has passed. It will be scheduled after the start of the next business hour.
|
|
Work order (TimeWindowGeoNode) already exists at ECO System. Please update or remove and add again.
|
An add operation is requested for the work order, but it is already present.
|
An update operation should be requested. Or, remove the work order and add it again.
|
|
Related Technician event (PillarTimeWindowGeoNode) Id passed is empty.
|
An existing technician event with location is being converted into an optimizable work order. But the related ID of the technician event is missing, so the operation is rejected.
|
|
|
Related Technician event (PillarTimeWindowGeoNode) Id passed is incorrect.
|
An existing technician event with location is being converted into an optimizable work order. But the related ID of the technician event is incorrect, so the operation is rejected.
|
|
|
Related Technician event (PillarTimeWindowGeoNode) found at ECO System, but not optimizable. Please remove and add again.
|
The related ID passed as part of the request to convert from fixed technician event to work order is found to be within the dispatch threshold time window.
|
Remove the event after the scheduled date and time of the event have passed, and add it again.
|
|
The element is supposed to be dispatched, but because of route inactivation became non-optimizable.
|
The work order was probably already within the dispatch threshold time window. But, before it could be marked as dispatched and synchronized, the route became unoptimizable because of manual scheduling. So, the work order is marked non-optimizable.
|
If the route is corrected and becomes active again, the correct dispatched schedule will be synchronized.
|