Subscribe to updatesFixed an issue that caused the Workspace to stop responding when loading the Node right-side navigation, creating or editing columns, or creating new Nodes.
Fixed an issue where commits could generate invalid YAML syntax because of incorrect indentation or missing escape characters in multi-line join statements.
We’ve focused this release on UI clarity, smoother onboarding, and CLI updates.
Clearer Join Error When a Source Is Missing — If you attempt to join to a source Node that doesn’t exist in Coalesce, the error message now explains exactly what’s missing and where to fix it.
Private Key Formatting Guidance — The Snowflake User Credentials screen now clarifies the expected private key format, reducing auth setup errors.
Skip Steps 2 and 3 — You can now skip steps 2 and 3 of the Onboarding Wizard when you already have those items configured, speeding up project setup.
Readable Errors and Warnings — The Coalesce CLI now formats deployment errors and warnings for easier scanning during runs.
Mixed JSON Key Types Could Drop Derived Columns — Resolved an issue where derived mappings omitted columns when JSON keys mixed data types.
Environment Deletion via API — Fixed an error that prevented deleting Environments using the API.
CLI Hang on Exit — Addressed a rare case where the CLI could hang after completing work.
Required Metadata Discard Error — Fixed an error thrown when discarding required metadata updates.
Introduced a newInsert Or Merge With Task Node type for the Streams and Tasks package.
Enables developing a stream on top of a table, view, or external table.
Adds an option to create a target table and insert or merge data from a source, with a task orchestrating the operation.
Other Updates For Streams and Tasks
Added comprehensive metadata update checks in create templates.
Fixed comment block parsing.
Updated node definition default scheduler option to prevent predecessor validation issues.
Added comprehensivemetadata update checks to the create templates flow to prevent mismatches during template generation.
Timestamp field uses a transform when configured.
Record versioning now supports integer columns.
When multiple timestamp columns exist, only the first selected column is considered.
With version 7.24, we have updated the supported Node.js versions for the coa CLI to ensure you are working in a stable and secure environment.
The coa CLI now supports the following Node.js versions:
20
22
24
Support for Node.js version 18 has been removed.
We removed support for Node.js version 18 because it is approaching its end-of-life. We have added support for version 24, a Long-Term Support (LTS) version, to ensure continued stability and security.
If you are running Node.js version 18, you must upgrade to a supported version (20, 22, or 24) to continue using the coaCLI. If you attempt to use the CLI with Node.js 18, it will exit with an error message stating that the version is not supported.
Coalesce has introduced updates to improve metadata integrity across Nodes. In this release, null values in Node metadata are automatically removed.
When you commit changes, you may notice updates to Nodes that you haven’t directly modified. This is expected, since null fields are being removed. You should commit these changes and continue with your workflow.
Git Modal: You may see diffs in the git modal where null values are removed.
No additional action is required. Commit the changes when they appear to keep your project in sync.
We’ve made a series of improvements focusing on UI consistency and run visibility.
Improved Display of Long Storage Location Names - Long storage location names in your build settings are now shortened to fit the screen. You can hover over the shortened name to see the full name in a tooltip.
Updated the "Re-Sync Source Columns" Window - We've updated the style of the "Re-sync Source Columns" window to match the rest of the application. It now provides a clearer message when there are no changes to sync.
Improved the "Delete Column" Confirmation - When you delete one or more columns, the confirmation window now clearly lists the columns you are about to delete. This helps you confirm your changes before they are made.
Updated Git View After Commit – The Git window has been improved so that after a successful commit and push, the view now clears automatically to show "No Files To View" This provides clearer feedback and ensures the view reflects the current state of your repository."
Added a "Rendering" Status for Runs - When you start a run, you will now see a "Rendering" status indicator. This provides better visibility into the run process, especially for large jobs that take time to render SQL before execution.
Added Tooltips to Run Details Page - On the Deploy and Refresh Runs page, you can now hover over truncated node names and error messages to see the full text in a tooltip.
Redesigned the Run Stage Details Window - We've redesigned the window that shows the details for a run stage. The new design makes it easier to read long SQL queries and error messages, with a wider layout and resizable panels.
Better Error Handling for Existing Git Branches - When creating a new workspace, you will now see a clear error message if the Git branch name you entered already exists, allowing you to choose a unique name.
Base Node Types – Advanced Deploy
Added comprehensive metadata update checks for Advanced Deployment Templates.
Fixed block comment issue for metadata update.
Streams and Tasks
Delta Stream Merge updates:
Dual merge logic implemented.
Redeployment behavior added for column schema changes.
External Table and External Iceberg Table supported as source objects.
Deployment phasing introduced.
Create Templates:
Added comprehensive metadata update checks.
Fixed comment block parsing.
Fixed default scheduler in node definition.
Running Nodes created with any version 2.2.0 and below without adding table key and partition key config options can cause rendering errors.
Create or Alter
Added comprehensive metadata update checks for Create Templates.
Fixed comment block parsing.
Fixed view issues caused by join changes.
External Table
Partitioning logic updated.
A default column PARTITION_COLUMN is added with the transformation:
split_part(metadata$filename, '/', 2) You can rename this column or adjust the transformation. You can also use another column with the right transformation for partitioning.
Prevented Deployments with Empty Column Names - To prevent errors, you can no longer deploy Nodes that have columns without names. The application will now show an error message, "Empty Column Names, during the deploy plan, prompting you to name all columns before deploying.
Fixed Drag-and-Drop for Jobs and Subgraphs - We fixed an issue where dragging and dropping nodes into a second or third Job or Subgraph would not work. You can now reliably add nodes to any Job or Subgraph using drag-and-drop.
Fixed Workspace Loading for Nodes with Invalid Configurations - We resolved an issue that prevented workspaces from loading if a node had an invalid configuration value. The application now automatically corrects these values to ensure your workspace always loads correctly.
Fixed Resizing of Include/Exclude Filters - We fixed a bug where the include and exclude filter boxes in the browser would shrink unexpectedly after being resized. Both filter boxes now resize correctly.
Fixed an issue where certain read-only editor fields could incorrectly be editable
Fixed an error preventing environments with large node counts from being deleted via API
Fixed an issue where nodes with null values caused blocking errors
With version 7.24, we have updated the supported Node.js versions for the coa CLI to ensure you are working in a stable and secure environment.
The coa CLI now supports the following Node.js versions:
20
22
24
⚠️ Support for Node.js version 18 has been removed.
We removed support for Node.js version 18 because it is approaching its end-of-life. 5We have added support for version 24, a Long-Term Support (LTS) version, to ensure continued stability and security. 6
If you are running Node.js version 18, you must upgrade to a supported version to continue using the coa CLI. After updating to release 7.24, running the CLI with Node.js version 18 will cause the CLI to exit with the following error message:
Invalid node version 18 not supported
We’ve made a series of improvements focusing on UI consistency, run visibility, and Git.
Improved Display of Long Storage Location Names - Long storage location names in your build settings are now shortened to fit the screen. You can hover over the shortened name to see the full name in a tooltip.
Updated the "Re-Sync Source Columns" Window - We've updated the style of the "Re-sync Source Columns" window to match the rest of the application. It now provides a clearer message when there are no changes to sync.
Improved the "Delete Column" Confirmation - When you delete one or more columns, the confirmation window now clearly lists the columns you are about to delete. This helps you confirm your changes before they are made.
Updated Git View After Commit – The Git window has been improved so that after a successful commit and push, the view now clears automatically to show "No Files To View" This provides clearer feedback and ensures the view reflects the current state of your repository."
Added a "Rendering" Status for Runs - When you start a run, you will now see a "Rendering" status indicator. This provides better visibility into the run process, especially for large jobs that take time to render SQL before execution.
Added Tooltips to Run Details Page - On the Deploy and Refresh Runs page, you can now hover over truncated node names and error messages to see the full text in a tooltip.
Redesigned the Run Stage Details Window - We've redesigned the window that shows the details for a run stage. The new design makes it easier to read long SQL queries and error messages, with a wider layout and resizable panels.
Better Error Handling for Existing Git Branches - When creating a new workspace, you will now see a clear error message if the Git branch name you entered already exists, allowing you to choose a unique name.
Prevented Deployments with Empty Column Names - To prevent errors, you can no longer deploy Nodes that have columns without names. The application will now show an error message, "Empty Column Names, during the deploy plan, prompting you to name all columns before deploying.
Fixed Drag-and-Drop for Jobs and Subgraphs - We fixed an issue where dragging and dropping nodes into a second or third Job or Subgraph would not work. You can now reliably add nodes to any Job or Subgraph using drag-and-drop.
Fixed Workspace Loading for Nodes with Invalid Configurations - We resolved an issue that prevented workspaces from loading if a node had an invalid configuration value. The application now automatically corrects these values to ensure your workspace always loads correctly.
Fixed Resizing of Include/Exclude Filters - We fixed a bug where the include and exclude filter boxes in the browser would shrink unexpectedly after being resized. Both filter boxes now resize correctly.
Base Node Types – Advanced Deploy
Added comprehensive metadata update checks for Advanced Deployment Templates.
Fixed block comment issue for metadata update.
Streams and Tasks
Delta Stream Merge updates:
Dual merge logic implemented.
Redeployment behavior added for column schema changes.
External Table and External Iceberg Table supported as source objects.
Deployment phasing introduced.
Create Templates:
Added comprehensive metadata update checks.
Fixed comment block parsing.
Fixed default scheduler in node definition.
Running Nodes created with any version 2.2.0 and below without adding table key and partition key config options can cause rendering errors.
Create or Alter
Added comprehensive metadata update checks for Create Templates.
Fixed comment block parsing.
Fixed view issues caused by join changes.
External Table
Partitioning logic updated.
A default column PARTITION_COLUMN is added with the transformation:
split_part(metadata$filename, '/', 2)You can rename this column or adjust the transformation. You can also use another column with the right transformation for partitioning.
Starting with the 7.24 release, we are updating the supported Node.js versions for the coa CLI to ensure you are working in a stable and secure environment.
The coa CLI will now enforce the use of the following Node.js versions:
20
22
24
⚠️ Support for Node.js version 18 will be removed.
We're removing support for version 18 because it reaches its end-of-life in April 2025. Support for version 24, a Long-Term Support (LTS) version, has been added to ensure continued stability and security.
If you are running Node.js version 18, you must upgrade to a supported version to continue using the coa CLI. After updating to release 7.24, running the CLI with Node.js version 18 will cause the CLI to exit with the following error message:
Invalid node version 18 not supported
Column lineage - We’ve improved the process by adding in app guidance and improving the visual indicators making it easier to see the propagation before commiting.
Snowflake Authentication - The Problem Scanner now alerts you when Snowflake authentication is missing.
Subgraphs and Jobs
The process for creating a Job or Subgraph is now easier. Enter a name in the modal, click Create, and you’ll be taken straight to your new Job or Subgraph.
We alert you in the Problem Scanner for duplicate Subgraph or Job names.
Previously, when a was Node was added or removed from a Subgraph it would be done silently. Now we let you know it was successful or failed along with either the Node name or number of Nodes.
When editing user roles, the role summary shows in the dropdown correctly.
Testing a Databricks SQL Warehouse connection will no longer fail with a "Missing token" error when a valid token has been entered.
Service accounts with Environment Admin permissions for Snowflake environments will no longer receive an "Invalid Connection Information" error on API calls.
Deploying a Storage Mapping change will no longer result in a "No schema found" error if the old schema or database was deleted directly from the data warehouse before deployment.
Deleting a source from a column now works consistently when using a trackpad or a mouse.
Sorting and filtering by Node Status or Stage Status on the deployment runs page will no longer revert or disappear on runs with a large number of objects.
Deleting a Source Node and creating a new table Node with the same name and location in a single deployment will no longer replace the existing table and cause data loss.
Understanding how transforms connect back to their source columns is now clearer and more intuitive. This update reduces confusion in the mapping grid by showing source details alongside transforms, giving you a complete and accurate view of column lineage.
Clear Source Visibility: When a transformation is applied, the corresponding column source details are displayed in a read-only, grayed-out format.
Hover for Full Details: Hovering over the source reveals:
The original table or alias used
All columns included in the transform
Automatic resolution of unqualified column names to their source tables
Hash Column Transparency: Hash columns now expand to show the list of underlying source columns.
Better Alias Handling: Joins using aliases now display clearer lineage, improving traceability.
Starting with the 7.24 release, we are updating the supported Node.js versions for the coa CLI to ensure you are working in a stable and secure environment.
The coa CLI will now enforce the use of the following Node.js versions:
20
22
24
Support for Node.js version 18 will be removed.
We're removing support for version 18 because it reaches its end-of-life in April 2025. Support for version 24, a Long-Term Support (LTS) version, has been added to ensure continued stability and security.
If you are running Node.js version 18, you must upgrade to a supported version to continue using the coa CLI. After updating to release 7.24, running the CLI with Node.js version 18 will cause the CLI to exit with the following error message:
Invalid node version 18 not supported
Column lineage - We’ve improved the process by adding in app guidance and improving the visual indicators making it easier to see the propagation before commiting.
Snowflake Authentication - The Problem Scanner now alerts you when Snowflake authentication is missing.
Testing a Databricks SQL Warehouse connection will no longer fail with a "Missing token" error when a valid token has been entered.
Service accounts with Environment Admin permissions for Snowflake environments will no longer receive an "Invalid Connection Information" error on API calls.
Deploying a Storage Mapping change will no longer result in a "No schema found" error if the old schema or database was deleted directly from the data warehouse before deployment.
Deleting a source from a column now works consistently when using a trackpad or a mouse.
Sorting and filtering by Node Status or Stage Status on the deployment runs page will no longer revert or disappear on runs with a large number of objects.
Deleting a Source Node and creating a new table Node with the same name and location in a single deployment will no longer replace the existing table and cause data loss.