> For the complete documentation index, see [llms.txt](https://help.ica.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.ica.illumina.com/reference/software-release-notes.md). # Software Release Notes This page contains the release notes for the current release. See the [subpages](/reference/software-release-notes/2025.md) for historic release notes. {% hint style="danger" icon="burst-new" %} IIllumina Connected Analytics is being renamed to **Illumina BioInsight Platform Core**. As part of this release, you will begin to see name changes across the Illumina software portfolio from ICA to Illumina BioInsight Platform Core or Platform Core. **There is no change to functionality under this rename, no changes to API structures, and backwards compatibility will be maintained.** Additionally, all references to **iCredits** are being **changed to** Illumina **BioInsight Credits (BIC)**. More information can be found in Illumina Product Change Notification ([PCN2026-1866](https://sharecontent.illumina.com/i/GihqYR4sJQkt62H4Tf6rw0vKP2SxHbFmAC___4eHin8IWMeQeDtEXvL6PLUSSIGNOt0mPLUSSIGNc3___DL26wgUV3IZs9jeH9X1kutzTsudNQaVBwTIODpnCeK1UPu4tlkYizMg1cMoh5EapPLUSSIGN)). Starting with the current release, references to Illumina Connected Analytics in the release notes will be changed to Illumina BioInsight Platform Core going forward. {% endhint %} ## 2026 September 30 - Platform Core v2.49.0 #### New Features and Enhancements * General * You can right-click and open [Project](/home/h-projects.md) pages in a new browser tab. * Base * \- * Bench * \- * Cohorts * \- * Data Management * When creating a new [project](/home/h-projects.md), Platform Core automatically selects a storage bundle using your entitlements for that region. * On /api/projects, the storageBundleId is optional (omit it for auto-assignment or pass a bundle id for backward compatibility). * The Project Data column picker now offers the [Pipeline](broken://pages/YmL5q15lUdOBb8ZIwbAD) and Pipeline version columns to display provenance without opening the output. * Flow * The [Pipelines](/project/p-flow/pipelines-new-view.md) page has a new look and feel that turns your list of pipelines into a customizable workspace. Instead of a single fixed list, you can now choose between tile or grid layouts, pin most-used pipelines to the top of the page, and assign an icon to each pipeline. * View pipelines as a grid of tiles or in rows. Switch between the two layouts to suit how you work. * Select the pipeline version directly from the tile or row drop-down without leaving the page. * Pin your favorite pipelines to the top of the list for easy access to the ones you run most often. * Give each pipeline its own icon so your team can recognize it quickly. * Pipeline [versions](/project/p-flow/pipelines-new-view.md#versions) are now managed together under a single pipeline name. Each pipeline shows its versions in one place, and you can select the version you want from the pipeline list or the pipeline details. Pipeline developers can add a version by cloning an existing one or using Save As, give each version a number and comment, edit that information afterwards, and move a version to another pipeline name. Versions without a version number are shown as Unversioned. Analyses record the pipeline version they ran, so you can see exactly which version produced a result. * Using the API, pipeline developers can [delete](/project/p-flow/pipelines-new-view.md#deleting-a-pipeline) pipelines they own that are in Draft, Archived, Import Failed, or Import Incomplete state. Analyses started from a deleted pipeline now indicate that the pipeline no longer exists. * DRAGEN pipelines are now available in Flow without requiring you to link a bundle to the project. * You can now have [preconfigured](/project/p-flow/f-analyses.md#use-parameter-presets) JSON-based pipeline input parameters and reuse them the next time you start an analysis. Instead of filling in the same fields from blank, apply a saved set to pre-fill the form and change only what you need. Saved settings are useful for pipelines you launch frequently or for sharing configurations with your team. * Pipeline developers can now [group input-form fields](/project/p-flow/pipelines-new-view/json-based-input-forms/inputform-json.md) into collapsible sections with either a checkbox or chevron to hide advanced or rarely used fields. * When cloning a pipeline through the API to create a new version, you can now set the version comment in the same request. #### Fixed Issues * General * The data search field now enforces a maximum search-text length of 250 characters, preventing errors from overly long search values. * Selecting a large number of images in the Docker repository is now significantly faster. * Fixed an issue where long report file paths could hide the Download button on the analysis Reports view. * Fixed an issue where disabled regions could be selected when creating a project. * Clearer API responses for invalid project permission updates and for duplicate or invalid Docker image names. * Base * Linking or synchronizing Base tables now runs in the background, so the interface stays responsive while the operation completes. * Bench * \- * Cohorts * \- * Data Management * Fixed an issue where data searches containing a wildcard (\*) could hang or return an unexpected error. * Fixed an issue where copy jobs that contained archived or partially archived files never completed because those files were included in the expected file count. * Large archived files now restore reliably, without delaying other operations on the same volume. * Files uploaded directly to your own storage bucket while a folder synchronization is running are now correctly identified as externally uploaded. * Restores started directly in your own S3 bucket are now recorded as external modifications, while restores started from Platform Core remain internal. * Fixed an issue where the project Data page failed to load when more than 200 copy or move jobs were running in the project. * Deleting multiple folders at once no longer takes disproportionately longer than deleting a single folder of the same size. * Sorting and paging deep into very large project file lists no longer disrupts data listing and search. * Flow * Nextflow pipelines now start in projects without internet access instead of timing out. * Fixed an issue where GET /api/pipelines returned a server error when generated pipeline codes exceeded the previous length limit. * Analyses can now be aborted reliably immediately after they are started, instead of the abort request being rejected while the analysis keeps running. * Fixed issues that prevented analyses on JSON input-form pipelines from being opened or started, including analyses created before ICA 2.48, pipelines whose onSubmit script returns no setting values, and non-repeatable field groups that lost their selected files. * Pipeline input-form tooltips now render markdown correctly, can be focused so you can select text and follow links, and no longer extend past the edge of the screen. * Fixed an issue where an automatically launched analysis could select an activation code without enough storage for the pipeline, causing the analysis to fail. * Samples * \- --- # 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://help.ica.illumina.com/reference/software-release-notes.md?ask=&goal= ``` `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.