> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/routing/logs-and-reports.md).

# Routing logs and reports

Use routing reports to explain who received a lead, why that person was selected, and how the pool is distributed over time.

**Open Queues → Assignment log** for workspace assignments. Open a queue for its **Usage log**, **Activity log**, and **Stats**.

## Find the right record

Start with the prospect, time, source, and workflow. Confirm the workspace and filters before comparing totals.

Use **Assignment log** for the individual decision. Use workflow **Logs** to see the surrounding journey, including CRM matching, qualification, and scheduling.

## Review a decision

Check:

1. The workflow and published version that handled the event.
2. The rulebook decision and matched rule, if one was used.
3. The queue, profile, and eligible members.
4. Skipped members and their reasons.
5. The selected member and any counted turn or refund.

A rulebook's **Logs** shows its inputs and the first matching rule. Its decision page links back to the workflow run when available.

## Explain uneven distribution

Equal weights do not guarantee identical meeting totals. Different eligibility, working hours, cancellations, no-shows, and ownership rules can produce different results.

Compare assignments within the same queue and period. Check whether the profile routes records, meetings, or both, and whether counts reset.

Review calibration separately from recorded turns. Calibration changes future priority; it does not edit assignment history.

## Choose the right log

| Log                                        | Answers                                         |
| ------------------------------------------ | ----------------------------------------------- |
| Workflow **Logs**                          | What triggered the journey and which steps ran? |
| Rulebook **Logs**                          | Which inputs and rule selected this route?      |
| Queue **Usage log**                        | How was this queue used?                        |
| Queue **Activity log** / **Routing audit** | Who changed routing configuration or status?    |
| Queue **Stats**                            | How is work distributed across the pool?        |
| **Bookings**                               | What happened to the meeting?                   |

For a failed external action, inspect the workflow step's delivery details. A successful assignment does not prove that a later CRM update or notification succeeded.

See [Workflow logs](/workflows/logs.md) for recovery and troubleshooting.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/routing/logs-and-reports.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 `build a script that syncs our docs to a CMS` 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.