> 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/nextseq-1000-2000/instrumentation-nextseq-1000-2000-troubleshooting-list/000007458.md).

# How to Troubleshoot "Error performing Sequencing\_ProtocolName\_Safestate" error on the NextSeq 1000/2000

**Background**

Users may encounter the following error during the first cycle of their NextSeq 1000/2000 runs:

*"There was an error performing Sequencing\_ProtocolName\_SafeState protocol. Contact Illumina Technical Support"*

This error message indicates that the run has terminated and that the consumables cannot be re-used. This error typically indicates a communication issue on the instrument that interrupted the run.

**Troubleshooting steps:**

1. Power cycle the instrument. Prepare a new flow cell while the instrument power cycles and reinitializes.
   1. For further information, see Illumina Knowledge Article [How to power cycle the NextSeq 1000/2000](/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-reference_material-list/000003038.md).
2. Once re-initialized, set up the run again with the same cartridge and a new flow cell.
3. If the instrument fails to initialize properly or the subsequent run fails during clustering, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for further troubleshooting guidance.

\
\
\ <br>

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