This guide provides a quick reference for common error codes encountered on the Urbantz platform, explaining what each error means, why it occurs, and how to address it.
Quick Navigation
- General Errors (000-xxx)
- Round Assignment & Fleet Errors
- Time Window & Scheduling Errors
- Integration Errors
General Errors
000-000: Unexpected Error
| Field | Details |
|---|---|
| Error Message | "Cannot read property..." or "An unexpected error occurred" |
| Explanation |
• General high-level error indicating something went wrong • Often occurs when task is in active collection but announcement is in archive • Can happen during optimization when fleet configuration has issues • May appear when using multiple tabs or windows |
| Solution |
• For task modification errors: Re-announce the task • For optimization errors: Check Fleet assignation for empty slots where vehicles were removed • Close all Urbantz tabs and windows, clear cache and cookies • If persistent, contact support with detailed error context |
000-005: Authorization Error
| Field | Details |
|---|---|
| Explanation |
• User lacks proper permissions or platform access • Multiple tabs or windows open with same account • Missing platform association in user profile • User might be associated with an inactive platform |
| Solution |
• Log out, close all Urbantz windows/tabs, clear browser cache and cookies • Log in using https://web.urbantz.com/portal/login • Only use one window/tab at a time • When associating platforms in admin section, only click SAVE at the TOP |
000-012: Duplicate Value Error
| Field | Details |
|---|---|
| Error Message | "Your request cannot be done because there's a double value" |
| Explanation |
Two users have the same phone number or email address. These values must be unique across all platforms as they can be used for login. |
| Solution |
• Ensure each user has a unique email address and phone number • Update the duplicate contact information to make it unique |
004-005: Invalid Action Error
| Field | Details |
|---|---|
| Error Message | "The specified action is invalid" |
| Explanation | Often caused by having the Route Editor (RE) open in multiple tabs while working |
| Solution |
• Close all but one tab with the Route Editor • Refresh the browser and try again • Avoid working in multiple tabs on the same function |
Round Assignment & Fleet Errors
005-007: Infeasible Optimization
| Field | Details |
|---|---|
| Error Message | "There was an error during round creation: infeasible optimization" |
| Explanation | Associated Platforms have mismatched configurations |
| Solution |
• Verify matching configurations across platforms • Ensure both platforms have identical dimensions, labels, and skills |
005-022: Optimization Mode Error
| Field | Details |
|---|---|
| Error Message | "The optimization mode is not available" |
| Explanation | Attempting to use "Preserve rounds and sequences" without proper settings |
| Solution |
• Go to optimization settings • Select "Optimize unassigned tasks" under available modes • Save settings • Now select "Preserve rounds and sequences" mode |
No Vehicles Found
| Field | Details |
|---|---|
| Error Message | "Unable to launch optimization: no vehicles found with provided configuration" |
| Explanation | Using a real fleet (not virtual) but no vehicles are set up |
| Solution |
• Go to Optimizations > Fleet Assignation • Set up at least one vehicle in the fleet • Save settings and try again |
Task Capacity Issues
| Field | Details |
|---|---|
| Error Message | "The round does not correspond to the characteristics required for a task" |
| Explanation | Issues with round task capacity, often due to an item volume value that is too large |
| Solution |
• Inspect affected tasks • Check associated item volumes • Adjust values to acceptable range for the platform |
Inadequate Fleet
| Field | Details |
|---|---|
| Error Message | "Inadequate fleet" |
| Explanation | Task requires labels that only vehicles with insufficient capacity have |
| Solution |
• Increase capacity of vehicles with matching labels • Or add labels to vehicles with sufficient capacity • Example: If a task with Label A needs weight 20, but the only vehicle with Label A has capacity 10, you'll get this error |
Time Window & Scheduling Errors
Multiple Time Windows Error
| Field | Details |
|---|---|
| Error Message | "No rounds were created due to an invalid format" or "The optimizer has failed due to an invalid input" |
| Explanation | Overlap in delivery time windows when multiple time windows are available |
| Solution |
• Check violation time parameter in advanced settings, you'll find that at: • Ensure Time Window 2 starts after Time Window 1 ends plus violation time • Add at least 1-minute buffer between windows • Example: With 30 min violation time, if Window 1 ends at 11:30, Window 2 should start after 12:01 |
Integration Errors
060-006: OAuth Authentication Failure
| Field | Details |
|---|---|
| Error Message | "OAuth authentication failed" |
| Explanation | OAuth failed to authenticate to the provider |
| Solution |
• Verify OAuth credentials and configuration • Check OAuth credential validity • Ensure provider service is operational |
422: Third-Party Error
| Field | Details |
|---|---|
| Error Message | "422: UNPROCESSABLE ENTITY" |
| Explanation | Issue originating from a third-party service, not from Urbantz |
| Solution |
• Document error context • Contact the relevant third-party service provider • Provide error details and logs |
General Troubleshooting Tips
- Avoid Multiple Tabs: Many errors occur when using multiple tabs or windows with the same account
- Clear Cache Regularly: For persistent UI issues, try clearing browser cache and cookies
- Check Configuration: Verify all settings in fleet and optimization configurations
- Contact Support: If issues persist, contact support@urbantz.com with error details (preferably a screenshot)
For errors not listed in this reference guide or if the suggested solutions don't resolve your issue, please contact our support team for further assistance.
Comments
0 comments
Please sign in to leave a comment.