> 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-x-x-plus/instrumentation-novaseq-x-x-plus-troubleshooting-list/000007994.md).
# How to Troubleshoot No Intensity or 0% Passing Filter at Inlet and Outlet Tiles on NovaSeq X Series
**Background**
Issues with sequencing runs presenting no Intensity or 0% Clusters Passing Filter for tiles at both the flow cell inlet and outlet are typically caused by skewed flow cell registration. The root cause for this can be either a transient flow cell seating issue, or issues with the flow cell clamping assembly.
**Figure 1**: 0% Intensity in Inlet and Outlet of Flow Cell Chart in Sequencing Analysis Viewer (SAV)
**Figure 2**. 0% Cluster Passing Filters in Inlet and Outlet of Flow Cell Chart in Sequencing Analysis Viewer (SAV)
**Troubleshooting Actions**
If a NovaSeq X Series sequencing run shows no Intensity or 0% Clusters Passing Filters in tiles at the flow cell inlet and outlet across all lanes, collect the following files from the instrument.
* Inspect the flow cell and flow cell stage for debris and clean using lint-free Contec Polynit Heatseal wipes as detailed in the [NovaSeq X Plus Product Documentation](https://support-docs.illumina.com/IN/NovaSeqX/Content/IN/NovaSeqX/Consumables.htm?Highlight=polynit)
* From the /usr/local/illumina/mnt/runs/\[RunID] directory, collect:
* RunInfo.xml
* InterOp directory
* Cycle 1 thumbnails for 1-2 affected lanes (**../Thumbnail\_Images/L00#/C1.1** directory where **#** is the Lane number)
* From the /usr/local/illumina/runs/\[RunID]/Logs/Logs.zip directory, collect:
* AutoCenterLineScan directory
Once these files have been collected, zip/compress them into a single file and then contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html) for next steps.
\
\
\
| |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #7994), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000007994%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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://knowledge.illumina.com/instrumentation/novaseq-x-x-plus/instrumentation-novaseq-x-x-plus-troubleshooting-list/000007994.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.