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. To route the activity, change either the dynamic routing time or activity limitations, or turn dynamic routing off. |
| 6003, 6077 | No appropriate resources | This means that the activity has requirements that can't be met by
any available resources. This message doesn't necessarily indicate an error. It
informs you that the application couldn't find a matching resource for the activity.
Check the following settings to confirm that they're 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. Fix the activity configuration. |
| 6007 | Unacceptable overdue | The activity wasn't 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 is overloaded or has not enough inventory | The activity was left unscheduled because of the Limit work by points parameter or lack of inventory. The assignment of this job would have caused a mobile worker to use extraneous inventory or incur more points than the 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. 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. To allow longer travel, change the Travel time settings in the routing plan. |
| 6011, 6013, 6063 | Linked activity cannot be scheduled | The activity is part of the group of linked activities and the group can't be assigned without link constraint violation. |
| 6016 | May cause SLA violation | Activity was unscheduled because it would cause a SLA violation by another following activity. It's 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's a very low chance to see this error code. |
| 6018 | Improper cost configuration | Activity wasn't routed due to improper cost configuration. For example, either its non-assignment cost is too low or resources' time and travel costs are too high. |
| 6019, 6079 | Activity cannot be assigned due to SLA restrictions | The activity wasn't 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. |
| 6020, 6070 | Provider preferences |
Activities can't be assigned without Provider Preferences violation. Insufficient Capacity: There's no available employee to handle the activity among required/allowed employees. |
| 6021 | May cause unacceptable overdue on other activities |
Assignment will cause unacceptable overdue on other activities. Insufficient Capacity: The activity assignment pushes another, more important or non-movable, activity into unacceptable overdue. |
| 6022 | May cause unacceptable overtime on other activities |
Assignment will cause unacceptable overtime on other activities. 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 can't make a route from the given activity to any of the activities in the route. This occurs due to an error in the data. Check the activity address, the coordinates, or travel key. |
| 6025 | Unacceptable travel distance | The activity was left unscheduled because the travel distance would have exceeded the maximum travel distance allowed. To allow longer travel, change the Travel distance settings in the routing plan. |
| 6027 | Segmentable activity was partially assigned | This message doesn't necessarily indicate an error. It informs you that the segmentable activity was partially assigned due to resource availability in combination with configured minimal and maximal length of a single segment. It may be a result of Insufficient Capacity and/or small maximal segment length. |
| 6028 | Unable to fit bundling policy constraints | Assignment will cause a violation of bundling policy constraints. If at least one bundled activity according to all-or-none bundling policy isn't assigned, it may cause non-assignment of the whole group of bundled activities. |
| 6094 | Activity location is missing | The travel-enabled activity can't be assigned due to its location not being specified either by coordinates or travel key. |
| 6032 | Travel statistics is missing | The travel can't be defined because the activity has a travel key only but required statistics is missing. |
| 6037 | Unacceptable daily travel distance | The activity was left unscheduled because the total daily travel distance exceeds the allowed value. |
| 6050 | Activity was removed from route while routing was running | Activity was removed from route while routing was running. |
| 6051 | Resource was removed while routing was running | Resource was removed while routing was running. |
| 6052 | Target route was deactivated while routing was running | Target route was deactivated while routing was running. |
| 6053, 20189 | Target route was changed while routing was running | Target route was changed while routing was running. |
| 6054, 6081 | Status of activity or activity segment was changed while routing was running | Status of activity or activity segment was changed while routing was running. |
| 6055 | Activity was moved while routing was running | Activity was moved while routing was running. |
| 6056 | Activity has no Work Zones | Activity has no Work Zones when the information is expected. |
| 6057 | Activity has no Work Skills | Activity has no Work Skills when the information is expected. |
| 6058 | Resource was deactivated while routing was running | Resource was deactivated while routing was running. |
| 6059 | Resource calendar was changed to non-working while routing was running | Resource calendar was changed to non-working while routing was running. |
| 6061 | Activity is not movable | Activity isn't movable according to the activity type configuration. |
| 6064 | Result is not accepted according to optimization criteria | This message doesn't necessarily indicate an error. The message means that the activity might be routed, but according to configured optimization criteria for chosen Optimization Goal, routing run was either not started or run results weren't applied. |
| 6067 | No required Work Zones |
No technicians with required Work Zones available. Insufficient Capacity: there aren't enough resources in the required work zone to handle the activity. |
| 6068 | No required Work Skills |
No technicians with required Work Skills available. Insufficient Capacity: there aren't enough resources with the required work skills set to handle the activity. |
| 6069 | No required inventory |
Technician doesn't have the required inventory. Insufficient Capacity: there aren't enough resources with the required inventory available to handle the activity. |
| 6071 | Not enough points | Technician doesn't have enough points to perform this activity. |
| 6072 | Calendar | Field Resources with matching working calendar aren't found. |
| 6073, 6074, 6075, 6076 | Appropriate field resources are not found |
It's the message from immediate routing that there are no field resources with active users or just field resources who may perform the activity. Insufficient Capacity: There are no available Field Resources to handle the activity. |
| 6084, 6085, 6086, 6087, 6088, 6089 | Resource cannot be used as a warehouse | Resource can't be used as a warehouse because it doesn't have Start Location, or working calendar, or inventory or other reason. |
| 6090 | Link constraints are not supported by chosen routing plan | Link constraints aren't supported by the chosen routing plan. |
| 6091 | The resource located outside of the routing bucket is partially excluded due to another run that is currently in progress. Please repeat the routing to include the resource. | The resource located outside of the routing bucket is partially excluded due to another run that's currently in progress. Repeat the routing to include the resource. |
| 6092 | Activity cannot be moved | Activity type constraints or routing plan settings prevent the activity from being moved between days and/or resources. |
| 6093 | Field Resources calendars and activity windows do not intersect | The activity's requirements can't be met by any available resource because there's no
intersection between available working calendars and activity SW/SLA. While this
error doesn't necessarily indicate an error, you should check the following settings
to confirm that they're 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 weren't included in the routing due to the absence of appropriate activities that could be allocated to them. |
| 20186 | Broadcast has timed out | An activity wasn't assigned within the allowed time for broadcasting. It may be a result of insufficient capacity when resources are fully loaded. |
| 20188 | No matching resources to broadcast | An activity wasn't assigned via broadcasting because there were no matching resources for it. |