> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/feature-highlights/queue-status-report.md).

# Queue Status Report

Need to check in on your queue and see what's currently going on? The Queue status report is your go-to spot! Most of the info here updates in real time, so you can easily see what your agents are doing or how many interactions are waiting. Just head over there to get the latest scoop!

<figure><img src="https://1039569329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lm5wszNs6c24n4NZ30U%2Fuploads%2FveSNxF9iTMhpUFcjoRwx%2FQueue%20Status%20Resized.gif?alt=media&amp;token=0b0a38ce-e9dc-42c5-b241-e4181a6d8093" alt="" width="375"><figcaption></figcaption></figure>

At the top, you'll spot some quick stats for each queue, showing how many interactions are waiting and how many are being answered by agents. You'll also see the number of agents available to take interactions. Clicking on any of these queue "cards" gives you detailed info right below. The agent tab shows you all agents in the queue and their current status. The interactions tab gives you a rundown of all the interactions in queue. The Link tab takes you straight to a prefiltered report for that queue.


---

# 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://cc.docs.landis.cloud/feature-highlights/queue-status-report.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.