> 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/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000007943.md).

# Troubleshooting the "Unable to load recipe" error on the NovaSeq 6000

When attempting to set up a run on the NovaSeq 6000, some users have reported an error stating: *"A problem occurred during run setup, unable to load recipes. to continue with run setup, reinstall the software suite"*. This error has also been reported to occasionally coincide with a second error stating: *"A problem occurred during run setup. Reenter the run parameters or contact technical support"*.

This issue is most commonly caused by improper run formatting during run setup. Specifically, these errors will occur if a run has an index length of 0 bp for the i7/Index 1 while having an index length of ≥1 bp for the i5/Index 2. While Illumina sequencers do support single-index run formats, they do not support solely using the i5/Index 2 and setting the i7/Index 1 length to 0 bp.

**Troubleshooting recommendations**:

1. The best option is to construct the library or libraries to be single-indexed with only the i7/Index 1 instead of the i5/Index 2. A single-indexed run using only the i7/Index 1 is supported on all Illumina instruments.
2. If the error persists after making the run format change, power cycle the instrument and re-attempt the run setup.
   1. For further information, search for Knowledge Base article [How to Power Cycle the NovaSeq 6000](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000002470.md).

If the above troubleshooting steps do not resolve the issue, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) with the following information:

* Intended run format (eg, 150 | 8 | 8 | 150, 100 | 8 | 0 | 100, etc.)
* NovaSeq Control Software Logs (C:\ProgramFile\Illumina\NovaSeq\NovaSeq Control Software\Logs)
* NovaSeq Run Setup Logs (C:\ProgramData\*\Illumina\NovaSeq\NovaSeqTemp\RunSetupLogs\[RunFolder])

\*The ProgramData folder may be hidden; to un-hide files, select the View tab in the file explorer window and make sure “Hidden items” is checked.

* Screenshot of the recipes listed at C:\ProgramFile\Illumina\NovaSeq\NovaSeq Control Software\Recipes\NovaSeq6000

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #7943), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000007943%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/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000007943.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.
