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

# Troubleshooting "Conflict" errors at the end of MiSeq runs

**Background**

MiSeq Control Software may display a Notification message stating "Conflict" during or shortly after the final cycle of a MiSeq run. Although this error typically prevents post-run analysis from starting automatically, it does not impact overall run performance.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-ae419b5061b73ef96d6bed4699ea607c2009a5a0%2Fimage1.jpg?alt=media\&token=65237f21-2ca5-492b-9661-93f33b522735)

A potential cause of this error is that the sample sheet is not present in the selected directory at the start of secondary analysis. This can occur if the sample sheet is selected from a temporary network location or USB flash drive at run start, and the sample sheet is no longer available in the temporary network location or the USB flash drive has been removed has been removed by the time secondary analysis begins.

To resolve this issue, requeue the analysis in Local Run Manager with a new sample sheet. For instructions to do so, please review the Illumina Knowledge Article [How to requeue and import run data for reanalysis with Local Run Manager](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001324.md).

\
\
\ <br>

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