> 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/000001388.md).

# Troubleshooting Possible Stale Image Data Detected on the NextSeq 500/550

The following warning occurs when issues arise during flow cell scanning in sequencing and can arise in imaging a single tile. It is usually reflected in poor sequencing metrics, such as overclustering, low passing filter, or a steep intensity/Q30 decline but does not cause the run to stop.

***Warning Occurred: Possible stale image data detected***\
***Warning Occurred: Saturated image data detected***\
![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-d43165d38e5824c61fd26d2fb0eb12284d174022%2Fimage1.png?alt=media\&token=4d120c31-fc7c-4c51-8dc6-d802b191c829)

**Troubleshooting steps:**

1. Evaluate run performance.
2. Complete automatic post-run wash.
3. Perform system checks.
4. Share results with [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/).

For reference, search Knowledge Base articles:

* [How to perform washes on the NextSeq 500/550](https://knowledge.illumina.com/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-reference_material-list/000003076.md)
* [How to perform a NextSeq 500/550 system check](https://knowledge.illumina.com/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-troubleshooting-list/000001883.md)

\
\
\ <br>

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