> 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/software/on-instrument-analysis-software/software-on-instrument-analysis-software-troubleshooting-list/000002415.md).

# How to remove a BCL file from analysis in MiSeq Reporter or Local Run Manager

Background: In situations where a single BCL file is corrupted or displays a high error rate, it is possible to remove the affected BCL from secondary analysis. This removes the affected tile at the impacted cycle from all downstream analysis.

Instructions:

1. On MiSeq, open D:\Illumina\MiSeqAnalysis\<run folder>\Data\Intensities\BaseCalls\L001
2. Open the folder for the affected cycle of the run.
3. Locate the BCL file for the affected flow cell tile.

a. For example, for tile 2103, the BCL file name is s\_1\_2103.bcl 4. Append .bak to the BCL file name.

a. For example, s\_1\_2103.bcl.bak 5. Requeue analysis of the run to repeat analysis with the problematic BCL file excluded from the results. For all of the clusters on the affected tile in the affected cycle, the base calls will be replaced with an N (no call).

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                 |
| :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #2415), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000002415%20-%20Software%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/software/on-instrument-analysis-software/software-on-instrument-analysis-software-troubleshooting-list/000002415.md?ask=<question>&goal=<endgoal>
```

`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.