> 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/emedgene/release-notes/workbench-and-pipeline-updates/new-in-emedgene-v100.40.0-march-30th-2026/v100.40-patches.md).
# V100.40 Patches
| Patches | Date | |
|---|
| V100.40.300 | September 30, 2026 | |
| V100.40.200 | June 24, 2026 | |
| V100.40.100 | May 13, 2026 | |
### V100.40.300 Update (September 30th, 2026)
#### Features
* Lab Tab | Removed limitation of 1000 regions for gene coverage download (limitation still exists in the UI).
#### Fixed Issues
* Add New Case | Fixed an issue where Add New Case for organizations with large gene lists was not returning results. Last 80 gene lists are displayed and all gene lists can be found in the search.
* Pipeline | General pipeline robustness improvements.
* Lab Tab | Fixed an issue where insufficient coverage for organizations with large gene lists was not returning results. Last 80 gene lists are displayed and all gene lists can be found in the search.
* \[Hotfix Aug. 3rd 2026] Analysis Tools | Fixed an issue where gene lists couldn’t be added to filters for customers with many gene lists. Last 80 gene lists are displayed and all gene lists can be found in the search.
* Curate | Fixed an issue where updating a variant in v100.40 from Analyze does not apply an ACMG automation version.
* Curate | Fixed an issue where batch upload silently failed to import variants with no error message. Errors are now accurately produced.
* Curate | Network | Fixed an issue where users couldn’t import variants from cross-cloud networks.
* Propagations from 100.39.700.
### V100.40.200 Update (June 24th, 2026)
#### Features
* Analysis Tools | The variant table saves user settings for columns, it will now also save the priority sorting. As a reminder, the default sort is by AI rank.
#### Fixed Issues
* Add New Case, Pipeline | Fixed multiple issues ingesting TruPath MRJD data from DRAGEN 4.5.
* Analysis Tools | Fixed an issue with Preset Filters including advanced Splice AI queries.
* Analysis Tools | Advanced filters has been renamed Query Builder and some UI issues have been fixed.
* Analysis Tools | Query Builder | Fixed an issue adding Phenomeld in sub-groups.
* Analysis Tools | Query Builder | Fixed issues with zygosity filters.
* Analysis Tools | IGV pop out | Fixed an issue where knowledgebase tracks were not selectable in the IGV pop out track settings.
* Variant Page | Fixed an issue where update Curate wasn’t working intermittently.
* Organization Settings | Fixed an issue where not all available Analysis Tools columns were available to configure.
* Propagations from 100.39.600.
### V100.40.100 Update (May 13th, 2026)
#### Features
* Improved support for TruPath DRAGEN 4.5 outputs:
* Added support for the TruPath phasing blocks phase\_blocks.gtf.gz file.
* Added support for TruPath MRJD VCF and JSON outputs.
* Added phasing filters.
* Added support for the DRAGEN Array 1.4 release.
#### Fixed Issues
* Pipeline | Fixed a rare issue causing cases to fail due to custom organization settings.
* Pipeline | Fixed an issue causing long processing times for cases loaded with BAM.
* Analysis Tools | Advanced filter operators | Fixed an issue where zygosity filters inherit from group operator and don't work as intended when starting with OR operator.
* Analysis Tools | Visualization | For TruPath BAMs, when toggling on phasing, each phase block will display with a different color.
* Propagations from 100.39.500.
---
# 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/emedgene/release-notes/workbench-and-pipeline-updates/new-in-emedgene-v100.40.0-march-30th-2026/v100.40-patches.md?ask=&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.