> 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/miniseq/instrumentation-miniseq-troubleshooting-list/000002236.md).

# Operational Qualifications Results upload prompt at end of run on the MiniSeq

A prompt to upload Operational Qualifications Results can be seen on the MiniSeq with Control Software (MnCS) v2.1.0.

After completing the first run after the software version is installed, a prompt appears asking to upload Operation Qualification (OQ) results to BaseSpace Sequence Hub (BSSH). Until a selection is made, the run will still show as Analyzing in BSSH.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-040032feb79d107c52d01ef887ad4a4f1a509b2f%2Fimage1.png?alt=media\&token=ce76da1c-c28d-4798-ada9-4b7896974848)

If the instrument is power cycled or the control software (MnCS) is exited between runs, this prompt will reappear after the next run.

These results are not critical for most users and are not required to be uploaded for the operation of the instrument. Select "Don't Ask Again" to prevent this pop-up in future runs.

\
\
\ <br>

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