> 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-500-550/instrumentation-nextseq-500-550-troubleshooting-list/000007529.md).

# Troubleshooting an Internal Temperature was Out of Range error on the NextSeq 500/550

The message typically does not stop the run, nor impact run performance. This error can result from a transient communication issue or a hardware related issue.

**The error message states:**\
*"The internal temperature of the instrument was out of range for more than one cumulative hour during the sequencing run. Review the quality metrics for the run. Refer to the user guide for more information..."*

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-e2cfca23c80dbc7fa829a339cd627a1ea9760418%2Fimage1.png?alt=media\&token=ed22cf89-740a-44b9-93d2-58ff0a1e2901)

**Troubleshooting steps:**

1. Allow the run to progress as normal and evaluate the run performance.
2. Upon run completion, complete the post-run wash.
3. Power cycle the NextSeq 500/550.\*
4. Complete a system check.\*
5. Contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/) with the system check results and the files listed below for further assistance.

Files to send to [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/):

1. System check results.
2. Run files.
   1. InterOp folder (entire folder)
   2. RunInfo.xml
   3. RunParameters.xml

\*For further information, search for Knowledge Base articles **How to Perform a NextSeq 500/550 Power Cycle** and **How to Perform a NextSeq 500/550 System Check**

\
\
\ <br>

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