> For the complete documentation index, see [llms.txt](https://docs.hedge.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hedge.video/canister/features/queuing.md).
# Queuing
## Setting up Queued Transfers
Queuing makes it quick and easy to stack up multiple transfers of the same type to each tape.
{% tabs %}
{% tab title="macOS" %}
{% hint style="info" %}
Canister for Mac disables Spanning mode when there is a queue and vice versa, Queuing when there is an active Spanning transfer.
{% endhint %}
Canister for Mac uses a separate Transfer List for Queued Archives and Retrieves. To add a new transfer click the Transfer List "+" button in the bottom left hand corner of the window, then work through the steps to add each additional transfer.
Rinse and repeat as many times as required. Canister will work its way through the each item in the queue until completion.
{% endtab %}
{% tab title="Windows" %}
{% hint style="info" %}
Canister for Windows will seamlessly segue from processing Queued Transfers into Spanning mode.
{% endhint %}
Canister for Windows uses the same Transfer List for Queued Archives and Retrieves. To add transfers click either Archive or Retrieve, then work through the steps to add each additional transfer.
Rinse and repeat as many times as required. Canister will work its way through the each item in the queue until completion.
{% endtab %}
{% endtabs %}
---
# 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.hedge.video/canister/features/queuing.md?ask=&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.
