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

# How to troubleshoot “Some of the settings may not be available when system activity is in progress” during run setup in MiSeq i100 Series

In some cases, after selecting **Start** in the MiSeq i100 Control Software (**Figure 1**), users may need to perform setting adjustments. For example, if the incorrect BaseSpace instance was selected or if a USB must be mounted for accessing a sample sheet.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-9ad9752cd8f826148a38b07642eff26d787f83b4%2Fimage1.png?alt=media)

**Figure 1.** Screen displayed after selecting **Start** from the MiSeq  i100 Series Control Software main menu.

If the Settings tab is opened after initiating Run Setup by selecting **Start**, the Control Software may display the warning message “Some of the settings may not be available when system activity is in progress”, and several settings options are unavailable (grayed out) (**Figure 2**).

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-324fcef425639dcd320e396149f8b42d256e431f%2Fimage2.png?alt=media)

**Figure 2.** Settings screen showing grayed-out options and the warning message at the bottom of the screen.

This behavior can occur when the user attempts to access the Settings option from the left‑hand menu while run setup is in progress. When **Start** is selected, the system immediately enters the run setup state, treats it as an active process, and limits the available settings options. To remove this warning and restore full access to the Settings menu, select the **Back** arrow (see Figure 1, left arrow) to exit run setup and re-enable all Settings options.

If the warning remains visible after exiting run setup, check the Runs Active tab for any ongoing background processes (e.g., data uploads or in-progress analyses) that may temporarily restrict access to certain settings.

\
\
\ <br>

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