Routing error messages
The following table provides the message codes:
| Error Code | Error | Explanation |
|---|---|---|
| 6000 | Dynamic routing | This is a common error that you can expect to see when using dynamic routing. It means the activity was filtered out because it falls outside the dynamic routing time or activity limitations. If you want to route the activity, change either the dynamic routing time or activity limitations, or turn dynamic routing off. |
| 6001 | Both work length and key are undefined | This is a data validation error. The application needs to know the estimated activity length. It can be specified either through stats or directly in the case of activities. If this error message displays it means this value is not specified and therefore the activity cannot be routed. You should never see this error message under normal circumstances. To correct this error specify the estimated activity length. |
| 6002 | Negative cost is not allowed | This is a data validation error. Activity cost is used as a multiplier for all activity related penalties and to implement activity priorities. You should never see this error message under normal circumstances. |
| 6003 | No appropriate resources | This means that the activity has requirements that cannot be
met by any available resources. This message does not necessarily
indicate an error. It informs you that the application could not find
a matching resource for the activity. Check the following settings
to confirm that they are accurate for your mobile workforce:
|
| 6005 | Service window start is greater than service window end | This is a data validation error. The service window end time falls before the service window start time on the activity. |
| 6007 | Unacceptable overdue | The activity was not scheduled because it would be late and
would start after the lateness settings specified in the filter parameters. Check the settings in the filter parameters. Go to the Filters section of the routing plan and click Settings to view filter parameters. |
| 6008 | Resource overloaded or has not enough resources | The activity was left unscheduled because of the Limit work by points parameter. The assignment of this job would have caused a tech to incur more points than his max threshold. You can adjust the resource’s point allotment in Daily View. |
| 6009 | Resource workday stop | The activity was left unscheduled because it would have caused overtime for the resource. If you want to allow overtime for resources, change the Resource Overtime settings in the routing plan. |
| 6010 | Unacceptable travel time | The activity was left unscheduled because the travel time would have exceeded the maximum travel time allowed. If you want to allow longer travel, change the Travel time settings in the routing plan. |
| 6011 | Linked activity cannot be scheduled | Activity was unscheduled due to the master activity in the linked activities (activity link) hierarchy. The activity was unassigned due to link requirements. |
| 6012 | Link Cycle | Activity was unscheduled for break dependency cycle between linked activities (activity link). |
| 6013 | Unable to fit activity link | Activity was unscheduled because the application was unable to find route that didn't violate linked activity requirements. |
| 6014 | Effective service window start is greater than effective service window end | This is a data validation error. After applying all time related constraints, the activity should be ended before it can be started. Usually, this occurs because of an error in the data. |
| 6015 | SLA window start is greater than SLA window end | This is a data validation error. Activity claims that the SLA window will end before/earlier than the SLA window will start. Usually, this occurs because of an error in the data. |
| 6016 | May cause SLA violation | Activity was unscheduled because it would cause a SLA violation by another following activity. It is normal to obtain this unscheduling reason when using SLA windows. |
| 6017 | Other | Reserved for cases where there are no other specific or precise unscheduling reasons. There is a very low chance to see this error code. |
| 6018 | Cost configuration | Activity was not routed as either its non-assignment cost is too low or resources' time and travel costs are too high. |
| 6019 | Unacceptable SLA overdue | Corresponds to the Unacceptable SLA Overdue protection. |
| 6020 | Provider preferences | Activities cannot be assigned without Provider Preferences
violation. Insufficient Capacity: There is no available employees to handle the activity among required/allowed employees. |
| 6021 | May cause unacceptable overdue on another activity | Assignment will cause unacceptable overdue on another activity Insufficient Capacity: The activity assignment pushes another, more important or non-movable, activity into unacceptable overdue. |
| 6022 | May cause unacceptable overtime on another activity | Assignment will cause unacceptable overtime on another activity Insufficient Capacity: The activity assignment pushes another, more important or non-movable, activity into unacceptable overtime. |
| 6024 | Unable to reach activity | Street level routing engine cannot make a route from the giving activity to any of the activities in the route. This occurs due to an error in the data. Other factors include travel restriction violations (if travel distance is over 200KM or 240 minutes, the error is returned). Check the activity address and the coordinates. |
| 6025 | Unacceptable travel distance | The activity was left unscheduled because the travel distance would have exceeded the maximum travel distance allowed. If you want to allow longer travel, change the Travel distance settings in the routing plan. |
| 6063 | Link constraint violation | Linked activities: Assignment will cause link constraint violation |
| 6064 | Result is not accepted according to optimization criteria | Routing run was either not started or run results were not applied because the conditions set for the given Optimization Goal were not met |
| 6067 | No required Work Zones | No mobile workers with required Work Zones available Insufficient Capacity: there is not enough resources in the required work zone to handle the activity. |
| 6068 | No required Work Skills | No mobile workers with required Work Skills available Insufficient Capacity: there is not enough resources with the required work skills set to handle the activity. |
| 6069 | No required inventory | Mobile Worker does not have the required inventory Insufficient Capacity: there is not enough resources with the required inventory available to handle the activity. |
| 6070 | Resource preferences | Assignment will cause Resource Preferences violation. See error code 6003 to understand and resolve this error. |
| 6071 | Not enough points | Mobile Worker does not have enough points to perform this activity |
| 6072 | Calendar | No providers with working calendar |
| 6077 | No mobile workers having right work skills and/or able to work in particular work zones found | The activity's requirements cannot be met by any available resource. While this
error does not necessarily indicate an error, you must check these settings to confirm
that they are accurate for your mobile workforce:
|
| 6092 | Activity is not movable | Activity type constraints or routing plan settings prevent the activity from being moved between days and/or resources. |
| 6093 | No mobile workers available calendar-wise to handle the particular activities found | The activity's requirements cannot be met by any available resource. While this
error does not necessarily indicate an error, you should check the following settings
to confirm that they are accurate for your mobile workforce:
|
| 6096 | Appropriate activities were not found | The routing report shows that this issue pertains to field resources rather than activities. This signifies that when the routing run was scheduled to commence, the field resources met the criteria but were not included in the routing due to the absence of appropriate activities that could be allocated to them. |