> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-troubleshooting-list/000008023.md).

# How to requeue analysis using only an index 2 (i5) read

**Note**:To requeue analysis with index 2 (i5) only, all i5 sequences in the pool must be unique.

To requeue with **GenerateFASTQ** in Local Run Manager:

* Edit the v1 sample sheet to use N as a wildcard base for index 1 (i7) and keep the index 2 (i5) sequences.

To requeue with **BCL Convert** in BaseSpace or locally on the instrument:

* BaseSpace does not accept N as a wild card base, but it allows for Override Cycles of index 1 if a v2 sample sheet is used. When generating a v2 sample sheet with BaseSpace Run Planning or Run Planning on the instrument, use "N" in the i7 index override cycles and delete all i7 sequences for the listed samples.
  * For example, if the original run set up is 251|10|10|251, the Override Cycles for the requeue should be set to Y251;N10;I10;Y251. For more information, see [How to use the 'OverrideCycles' setting in the Run Planning User Interface](https://knowledge.illumina.com/software/general/software-general-faq-list/000005671.md).

To requeue with **bcl2fastq**:

* For detailed steps, see [How to demultiplex a run without using either the i7 index or the i5 index using bcl2fastq2](https://github.com/illumina-swi/illumina-knowledge/tree/master/docs/Software/On-Premises-Software/Reference_Material/000003145.md).

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #8023), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000008023%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/instrumentation/general/instrumentation-general-troubleshooting-list/000008023.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.
