> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/retail-operations/orders/order-routing/troubleshooting.md).

# Troubleshoot order routing

Diagnose common order routing schedule, facility, inventory, and shipping-method issues.

Start with the routing group that should have processed the order. Confirm that you selected the correct Product Store in the app footer, then use the symptom table to continue.

```mermaid
flowchart TD
    accTitle: Choose the right order routing troubleshooting guide
    accDescr: Use routing group history to distinguish a missing run from a completed run. For a completed run, investigate order selection, facility configuration, or inventory according to the observed symptom.
    A["Open intended group History"] --> B{"Expected run recorded?"}
    B -->|No| C["Check schedule and job status"]
    B -->|Yes| D["Review run outcome"]
    D -->|Order did not match| E["Order filters and shipping mappings"]
    D -->|Unexpected facility| F["Facility configuration"]
    D -->|No or partial allocation| G["Inventory availability and rules"]
```

| Symptom                                                              | Check                                                                                                                                                                |
| -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A routing group did not run                                          | [Troubleshoot a routing schedule](https://docs.hotwax.co/documents/retail-operations/orders/order-routing/troubleshooting/scheduling-error.md)                       |
| A facility was skipped or selected unexpectedly                      | [Troubleshoot facility configuration](https://docs.hotwax.co/documents/retail-operations/orders/order-routing/troubleshooting/incorrect-facility-configurations.md)  |
| An order did not match the intended shipping-method filter           | [Troubleshoot shipping-method mapping](https://docs.hotwax.co/documents/retail-operations/orders/order-routing/troubleshooting/incorrect-shipping-method-mapping.md) |
| A routing rule found no inventory or allocated only part of an order | [Troubleshoot inventory availability](https://docs.hotwax.co/documents/retail-operations/orders/order-routing/troubleshooting/inventory-unavailability.md)           |

Use `History` on the routing group detail page to separate schedule problems from routing outcomes. A completed run with no allocation usually points to the routing, routing-rule, inventory, or reference-data configuration rather than the schedule.

See [Order routing](https://docs.hotwax.co/documents/retail-operations/orders/order-routing.md) for the routing group, routing, and routing-rule hierarchy.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hotwax.co/documents/retail-operations/orders/order-routing/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
