> 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/scheduling-error.md).

# Troubleshoot a routing schedule

Diagnose a routing group that did not run at the expected time.

Use the routing list, schedule details, and run history to determine whether the problem is the schedule or the routing configuration.

## Check the schedule

1. Open the **Order Routing Rules** app.
2. Confirm the Product Store and time zone shown in the app footer.
3. Go to `Routing` > `Order Routing`.
4. Use the `Active` and `Draft` tabs to find the routing group.
5. Open the routing group.
6. Confirm that its status is `Active`.
7. In `Scheduler`, confirm that a schedule exists and review the displayed cadence and `Next run`.
8. Save or discard any pending configuration changes.
9. Click `Edit schedule` when the cadence or Quartz cron expression is incorrect.
10. Select a schedule option or update `Expression`, click the save icon, then confirm `Save`.

The schedule editor previews the expression in the user's displayed time zone, but the saved job runs in the default time zone of the HotWax Commerce server. Compare the saved `Next run` and `History` values, then confirm the server time zone with your system administrator before you change a schedule that appears offset.

## Check active configuration

A scheduled routing group can run without allocating orders when its child configuration is inactive or does not match an order.

1. Confirm that the required routing has an active status.
2. Confirm that the required routing rules have an active status.
3. Review the routing's order filters.
4. Review the routing rules' facility filters and unavailable-item actions.
5. Save any changes.

## Compare a manual run with history

1. Click `History` and look for the expected scheduled start.
2. If no entry exists, return to the schedule and status checks.
3. Click `Run now` to start an immediate copy of the routing group.
4. Open `History` again and inspect the new run.

`Run now` does not replace or change the saved schedule.

* If the manual run completes, focus on the schedule, status, and time zone.
* If the manual run starts but allocates no orders, inspect routing filters, routing-rule filters, inventory, and queue actions.
* If the manual run fails, capture the run time and routing group ID for operational investigation.

The `Coverage by day and hour` chart on the Order Routing List page can also reveal schedule gaps. See [Manage routing groups](/documents/retail-operations/orders/order-routing/manage-and-configure/brokering-runs.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://docs.hotwax.co/documents/retail-operations/orders/order-routing/troubleshooting/scheduling-error.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.
