Flowtlas · Guide
Why did this job not fit the route plan?
Unassigned work means the returned plan did not allocate that task. Start with the reported reason and the task's actual requirements. Different problems need different corrections; increasing the search time does not make an ineligible vehicle suitable for a job.
Discuss your planning workflowThese examples explain planning capabilities. Contact us to confirm availability and integrations for your workspace.
Review the inputs in a useful order
- Eligibility: does any selected tour have the required people, skills and allowed vehicle?
- Capacity: are the load units, starting load and signed stop changes correct?
- Time: do work windows leave time for driving, waiting and service inside the supplied rules?
- Relationships: do ordered stops, gap rules or commitments conflict with the rest of the work?
- State: are recorded vehicle positions and loads valid and current enough for this request?
Read the result without assuming more than it says
| Reported status | Meaning | Next step |
|---|---|---|
| Complete | All active tasks are covered in the returned result | Review the route and inputs; this is not proof of global optimality |
| Partial | Some work remains unassigned under the permitted policy | Review the tasks and reason categories |
| NoSolutionFound | The bounded search did not find a solution | Check constraints and data; do not assume mathematical impossibility |
| Infeasible | A hard contradiction was established | Resolve the reported contradiction before solving again |
Example: the missing specialist
A service task requires a specialist skill, but none of the selected tours has that skill. First check whether the right people were selected and whether their skill data is correct. If no eligible team is actually available, the operational choice is to change availability, reschedule or otherwise handle the work. Removing a real requirement only makes the input less accurate.
Reasons guide investigation
The engine exposes categories including no eligible tour, capacity, time window, route infeasibility, agent rejection and invalid live state. Treat them as diagnostic starting points; they do not necessarily isolate every conflicting requirement in the request.
Frequently asked questions
Why can some work remain unassigned?
Work may lack an eligible tour or fail to fit capacity, time or route constraints. When the request permits partial work, the result can report unassigned tasks and reason categories. Review those reasons together with the task and resource data.
Does “NoSolutionFound” mean the job is impossible?
No. It means the bounded search did not find a solution. Review the inputs, constraints and search budget. This differs from an infeasible result based on an established hard contradiction.
Does a complete plan mean it is the shortest possible route?
No. Complete describes coverage of active tasks in the returned result. It does not prove global optimality. Compare the result using your actual constraints and a reproducible baseline before making any efficiency claim.
How much time or distance will this save?
That depends on the operation and the baseline. Use the same work, resources, constraints and travel assumptions to compare plans. A percentage saving or fixed solve-time guarantee needs measured evidence from a representative run.