> 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/miseq-ruo/instrumentation-miseq-ruo-troubleshooting-list/000005566.md).

# Troubleshooting a MiSeq "Consecutive Camera Failure Limit has been Exceeded for this Run" error

The Consecutive camera failure limit has been exceeded for this run error reported on MiSeq Control Software (MCS) v4.0 and higher is a generic error message related to any hardware involved with the execution of the tile scan.

**Error message in MCS v4.0**:

"Consecutive camera failure limit has been exceeded for this run. The run is being aborted. Contact Technical Support."

**Troubleshooting:**\
In order to effectively troubleshoot this error message, send the following files by email to Illumina Technical Support (TS) at <techsupport@illumina.com> for evaluation and the next steps.

From within D:\Illumina\MiSeqTemp\&lt;run folder>, collect files:\
InterOp folder\
Logs folder\
RunParameters.xml\
RunInfo.xml

Once these files have been provided, do the following:

* Power cycle the instrument.
  * For further information about power cycling the MiSeq, search Knowledge Article [How to Power Cycle the MiSeq.](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md).
* Perform a manual post-run wash and wait for further guidance from Technical Support.
  * For further information about performing manual washes on the MiSeq, search Knowledge Article [Best Practices for Washes on the MiSeq](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001679.md).

\
\
\ <br>

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