> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/dragen-mirna/faq/known-issues-and-limitations.md).

# Known Issues and Limitations

## DRAGEN miRNA 1.0.0

### Known Issues​<br>

* Sample-level metrics: DRAGEN Reports currently do not display sequencing quality graphs at the sample level.
* UMI support: DRAGEN Reports currently display metrics for Reads, but not for Unique Molecular Identifiers (UMIs).​ Please refer to the UMI output files (e.g., all\_samples.miRNA.UMIs.txt) for UMI-specific information.​
* Summary file counts: In the files all\_samples.V1.summary.xlsx and all\_samples.V1.summary.txt, the reported total reads​ for each small RNA type (e.g., miRNA\_Reads, hairpin\_Reads, piRNA\_Reads, rRNA\_Reads, tRNA\_Reads, mRNA\_Reads) represent​ the sum of all reads mapped to that RNA category. However, only small RNAs with at least 10 read matches are listed in​ the individual small RNA output files.•

### Known Limitations​ ​

* RNA detection is restricted to the reference sequences provided by the software for the supported model organisms.​ Custom or user-supplied references are not supported.​
* Only RNAs included in the reference database are detected; the software does not support discovery or prediction of​ novel or unannotated RNAs.


---

# 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://help.bioinsight.illumina.com/dragen-mirna/faq/known-issues-and-limitations.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.