User Level Debugging Guide
- eknoor.singh (Unlicensed)
- Hitesh Sarup
Users can refer to this document to understand how to debug an user-level errors experienced with the Route Optimiser.
Dropped Reason Bucket | Reason Type | Possible RCA | Input error (if present) | Possible next steps |
|---|---|---|---|---|
Eligible vehicle list is empty | Primary | Hub doesn't have vehicles mapped to it in Setup -> Vehicle Master | Hub doesn't have vehicles mapped to it in Setup -> Vehicle Master | If vehicles are not mapped due to human error , need to add vehicles in Setup -> Vehicle Master |
Available For Planning,Available For Local Trips,Available For Upcountry these keys might not be set as true in vehicle master | Keys are not turned true for the vehicles by mistake or due to lack of proper understanding | Make the above keys true for intended vehicles | ||
Required fields (lat , lng) not specified | Primary | Address details are empty along with destination/origin lat-long . Both cant be empty together | User missed to update address and lat long both in the softdata upload | Edit the consignment details from CRM and fill the lat long before sending it for routing again |
If running on demo environment, the batch size is too big | - | - | ||
Geocoding service failed. Due to poor address quality/missing fields. | - | - | ||
Insufficient weight. Required: {consignment[‘weight’]}, Max available: {maxVehicleWeightCapacity} | Secondary | Total vehicle weight might not be sufficient to pick all consignments | Vehicle list must be less than the intended vehicle list. | Go to Setup -> Vehicle Master, check if the list of vehicles is same as the on ground available vehicles for that hub. If yes then check if there are already unintended trips created on the dashboard which might make the vehicle already busy and hence not considered by optimiser |
If using other constraints like time, tags , partition etc . The consignment might not be able to fit into vehicles that have picked consignments which meet the above mentioned constraints. | Weight of some consignments is abysmally high due to input error | Check consignment for which the weight is not as it should be(generally higher, may even be lower). Correct the weight of the consignment using edit option in CRM.Weight of consignments should reflect the actual weight of consignment on ground | ||
Input Vehicle weight capacity might be wrong | Correct the input vehicle weight | |||
Insufficient volume. Required: {consignment[‘volume’]}, Max available: {maxVehicleVolumeCapacity} | Secondary | Total vehicle volume might not be sufficient to pick all consignments | Vehicle list must be less than the intended vehicle list. | Go to Setup -> Vehicle Master, check if the list of vehicles is same as the on ground available vehicles for that hub. If yes then check if there are already unintended trips created on the dashboard which might make the vehicle already busy and hence not considered by optimiser |
If using other constraints like time, tags , partition etc . The consignment might not be able to fit into vehicles that have picked consignments which meet the above mentioned constraints. | Volume of some consignments is abysmally high due to input error | Check consignment for which thevolume is not as it should be(generally higher, may even be lower). Correct the weight of the consignment using edit option in CRM.Volume of consignments should reflect the actual volume of consignment on ground | ||
Input Vehicle Volume capacity might be wrong | Correct the input vehicle volume in Setup -> Vehicle Master | |||
Insufficient consignment capacity. Required: {consignment[‘consignments_count’]}, Max available: {maxVehicleNumberCapacity}. | Secondary | Total consignment capacity of vehicles might not be sufficient to pick all consignments | Vehicle list must be less than the intended vehicle list. | Go to Setup -> Vehicle Master, check if the list of vehicles is same as the on ground available vehicles for that hub. If yes then check if there are already unintended trips created on the dashboard which might make the vehicle already busy and hence not considered by optimiser |
If using other constraints like time, tags , partition etc . The consignment might not be able to fit into vehicles that have picked consignments which meet the above mentioned constraints. | Input Vehicle Consignment capacity might be wrong | Correct the input vehicle consignment capacity in Setup -> Vehicle Master | ||
Insufficient length. Required: {consignment[‘length’]}, Max available: {maxVehicleLength}. | Primary | Consignment length is greater than vehicle length | Either consignment length might be given too large or vehicle length might be given too small | Edit consignment details in CRM or Edit Vehicle details in Setup -> Vehicle Master. |
Insufficient width. Required: {consignment[‘width’]}, Max available: {maxVehicleWidth}. | Primary | Consignment width is greater than vehicle width | Either consignment width might be given too large or vehicle width might be given too small | Edit consignment details in CRM or Edit Vehicle details in Setup -> Vehicle Master. |
Insufficient height. Required: {consignment[‘height’]}, Max available: {maxVehicleHeight}. | Primary | Consignment height is greater than vehicle height | Either consignment height might be given too large or vehicle height might be given too small | Edit consignment details in CRM or Edit Vehicle details in Setup -> Vehicle Master. |
Consignment roundtrip breaches time window of all vehicles. | Primary | Consignment is very far away from hub and all vehicles will not be able to pickup and come back from the hub without violating the delivery time window | Either consignment is actually far away incase nothing to be done but geocoding might be wrong due to any reason. | Edit CRM details by correcting the lat long. Ensure address quality is good and fields are not missing at time of softdata upload. |
Consignment roundtrip breaches distance capacity of all vehicles. | Primary | Consignment is very far away from hub and all vehicles will not be able to pickup and come back from the hub without violating the distance limit of the vehicle | Either consignment is actually far away incase nothing to be done but geocoding might be wrong due to any reason. | Edit CRM details by correcting the lat long. Ensure address quality is good and fields are not missing at time of softdata upload. |
Minimum pickup time window open in pickup time slot list is later than max vehicle close time. Open: {consignment[‘pickup_time_slot_list’][0][0]}, vehicle close: {maxVehicleCloseTime}. | Primary | The pickup time window doesn't coincide with any of the vehicle service time window | Self Explanatory | Self Explanatory |
Minimum time window open in time slot list is later than max vehicle close time. Open: {consignment[‘time_slot_list’][0][0]}, vehicle close: {maxVehicleCloseTime}. | Primary | The delivery time window doesn't coincide with any of the vehicle service time window | Self Explanatory | Self Explanatory |
Maximum pickup time window close in pickup time slot list is earlier than min vehicle open time. Close: {consignment[‘pickup_time_slot_list’][-1][1]}, vehicle open: {minVehicleOpenTime}. | Primary | The pickup time window doesn't coincide with any of the vehicle service time window | Self Explanatory | Self Explanatory |
Maximum time window close in time slot list is earlier than min vehicle open time. Close: {consignment[‘time_slot_list’][-1][1]}, vehicle open: {minVehicleOpenTime}. | Primary | The delivery time window doesn't coincide with any of the vehicle service time window | Self Explanatory | Self Explanatory |
None of the vehicle has required constraint tags. Required: {set(consignment[‘constraint_tags’])} | Primary | If tags is passed as a constraint then no vehicle contains the constraint tags that are passed for vehicles. | Vehicle master isn't updated with the correct constraint tags. | Vehicle Master needs to be updated with the correct constraint tags. |