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

# Troubleshooting Issues with Waste Level Sensor System Check on the MiSeq i100 Series

**Background**

The MiSeq i100 Series uses a sensor to measure the weight of the waste bottle and report if the spent reagents bottle needs to be emptied prior to starting a sequencing run. The Waste Level Sensor check under the Enclosure System Checks verifies that this sensor is working as expected.

See the following steps to troubleshoot the Waste Level Sensor check if this test is unable to pass during the instrument System Health Checks process.

**Troubleshooting Actions**

1. Repeat the instrument system checks to verify if issue is persisting.
   1. Select **Clear Checks** and return to the System Check home screen.
   2. Select the **Enclosure** system checks.
   3. Select **Next**.
   4. When prompted, confirm that the spent reagents bottle is completely empty.
      1. If available, load the unused spare spent reagents bottle that comes with the instrument. This ensures that the waste bottle is completely empty of any spent reagents.
   5. Select **Start Checks** to proceed with repeating the Enclosure System Check.
2. If the **Enclosure** System Health Check is unable to pass on the second attempt, **power cycle** the instrument.
   1. See Knowledge Article [How to Power Cycle the MiSeq i100 Series](https://knowledge.illumina.com/instrumentation/miseq-i100-series/instrumentation-miseq-i100-series-reference_material-list/000009277.md) for additional details.
3. Repeat the **Enclosure** System Health Check after instrument has rebooted and initialized.

If the Waste Level Sensor system check shows persisting issues after performing Troubleshooting Actions, run the **Export Logs - Small** workflow to bundle the system check report and logs. See Knowledge Article [How to Export Logs on the MiSeq i100 Series](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000009265.md) for additional details.

Once the Export Logs process has completed, contact [Illumina Tech Support](https://www.illumina.com/company/contact-us.html) for further assistance.

\
\
\ <br>

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