> 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/000009702.md).

# Unlocking a Locked Cloud Planned Run on the MiSeq i100 Series

**Background**

The MiSeq i100 Series allows users to use the BaseSpace Run Planning tool to plan Sequencing Runs and Secondary Analysis. After logging into the instrument using the Cloud account, the Planned Run is available on the MiSeq i100 Series instrument. If there is an issue during Run Setup, the Planned Run can get stuck in a "locked" state. If this occurs, see the following Troubleshooting Actions to resolve this issue.

**Troubleshooting Actions**

Planned Runs can only be unlocked by a User Account with local Administrator privileges. As Cloud Users are Sequencing Operator accounts by default, they do not have the appropriate permissions to unlock a Cloud Planned Run. See the following steps to elevate a Cloud User to an Administrator account to unlock Cloud Planned Runs.

1. Log into the instrument under a local **Administrator** account
2. Select the **dropdown menu** in the top-left corner, then select **Settings**, then **Users**.
3. In the **Users** User Interface (UI), select the Cloud User account associated with the locked Planned Run.
4. In the **Edit User** UI, select the checkbox next to **Administrators**, then select **Save**.
5. Log out of the local Administrator account
6. Log into the Cloud account, then navigate to **Runs** and unlock the Planned Run.

If the Cloud User is not able to unlock the Planned Run after being provided Administrator rights, contact [Illumina Tech Support](https://www.illumina.com/company/contact-us.html) for further guidance.

\
\
\ <br>

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