> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner/troubleshoot-route-optimization.md).

# Troubleshoot route optimization

Route optimization can fail for several reasons.

The error message usually points to the cause.

### Common errors

#### Not enough time to travel from depot

The work order cannot be reached within the available schedule.

#### Time window start must be before end

A work order has an invalid time window.

#### Not all work orders are planned

Some work orders could not be assigned.

#### Request size exceeded

The optimization contains too much data in one run.

#### Unexpected error occurred

A general error stopped the optimization.

### How to resolve the most common issues

{% stepper %}
{% step %}

### Check schedules and availability

Make sure employee working hours match the planning demand.
{% endstep %}

{% step %}

### Check address quality

Verify that all work orders and start locations have valid coordinates.
{% endstep %}

{% step %}

### Check time windows

Make sure each time window has a valid start and end.
{% endstep %}

{% step %}

### Reduce the run size

Split large runs by day, team, or group if needed.
{% endstep %}

{% step %}

### Retry the optimization

Start a new run after you adjust the blocking data.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
If available, download debug data and attach it to your support request.
{% endhint %}

### Frequently asked questions

<details>

<summary>Where do I see the error message?</summary>

In the PlanSmart results panel after the run ends.

</details>

<details>

<summary>Can I download debug data?</summary>

Yes.

Use it when support needs more detail.

</details>

<details>

<summary>What should I do if the run keeps failing?</summary>

Review the blocking data and contact support with the debug data.

</details>

### Related topics

* [**PlanSmart (AI Routeplanner)**](/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner.md)
* [**Start route optimization from the planboard**](/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner/start-route-optimization-from-the-planboard.md)
* [**Set up PlanSmart with the setup wizard**](/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner/set-up-plansmart-with-the-setup-wizard.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/plansmart-ai-routeplanner/troubleshoot-route-optimization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.