Subscribe to updatesWe’ve introduced a new feature that lets you know when a Node or Column Test has failed during a refresh.
On the Deploy page, statuses are now color coded for easy review.
Green - It was successful with no errors.
Yellow - The Refresh was successful, but had Column or Node test failures.
Red - The Deploy or Refresh failed.
Take a look at Troubleshooting Deploys and Refreshes.
We’re excited to launch our Intelligent Documentation Assistant – a smarter, faster way to document your data workflows.
Maintaining clear and consistent documentation across pipelines is always a challenge. Coalesce makes it effortless by automatically generating natural language descriptions from your lineage and transformation metadata to create:
Node & Column Descriptions: Auto-generated, easy-to-understand explanations of column transformations, logic, and business context — no more manual notes or guesswork.
AI-Generated Git Commit Messages: Helpful, context-aware commit messages to keep your Git history clean, descriptive, and useful.
Reduce Documentation Overhead: Free up time for development while Coalesce handles the docs.
Maintain Consistency: Ensure standardized documentation across all data projects, teams, and environments.
Improve Stakeholder Clarity: Make it easier for business users and analysts to understand transformation logic.
Accelerate Onboarding: Help new team members ramp up faster with auto-generated, clean documentation.
AI Features not enabled by default in Coalesce. Organization admins can opt-in to the AI Documentation Assistant by going to Org Settings > Preferences and toggling AI Features.
These features are currently in Private Preview. Please reach out to your Coalesce account manager to sign up.
We’ve introduced a new feature that lets you know when a Node or Column Test has failed during a refresh.
On the Deploy page, statuses are now color coded for easy review.
Green - It was successful with no errors.
Yellow - The Refresh was successful, but had Column or Node test failures.
Red - The Deploy or Refresh failed.
Take a look at Troubleshooting Deploys and Refreshes.
You can now use OAuth to run concurrent jobs using the Snowflake Tasks API.
You can now type to search within all dropdown filter menus on the Deploy page, making it faster and easier to find the option you’re looking for.
Previously credential errors and mismatches would return a 500 for the`startRun` endpoint.`startRun` now returns either a400 or 401.
We fixed an issue where an invalid project ID would make the application unresponsive.
[Object Object] no longer appears in the hash column.
Version 7.16.1
Column Lineage now renders correctly.
Fixed an issue where createdAt and updatedAt fields in and older version of packages caused deployment failures.
Deprecated node metadata changes were completed with the release of 7.15.
Previous posts
March 13, 2025 - Upcoming Deprecated Node Metadata Changes
March 3, 2025 - Deprecated Node Metadata Changes
The coa CLI will now display plan warning messages even if the plan was successfully created. This will help you identify any issues that come up before deployment.
The /api/v1/environments/{environmentID}/nodes and /api/v1/workspaces/{workspaceID}/nodes endpoints now have pagination. You can use the following query parameters to organize your responses:
Limit - The maximum number of Nodes to return.
startingfrom - The cursor point for paging the query results.
orderBy - The field to order the results by.`
Version 7.15.1
Turning off the multi-source toggle will now properly remove the additional source from the YAML file.
[Object Object] no longer appears in the hash column.
Column lineage will now display a loading spinner and will only render when column lineage is ready.
In our ongoing efforts to enhance performance and maintainability, we're removing some legacy metadata fields that are no longer needed.
This process is happening in two stages:
Release 7.14 - Already completed ✅
Release 7.15 - Coming soonCompleted on March 18, 2025 ✅.
What this means for you:
No workflows will be disrupted.
No data will be affected.
When doing a commit, you might see changes for Nodes that you haven’t modified. This is expected when deprecated metadata is removed. You will need to:
Making a commit with the changes.
Continue on with your workflow.
Example of a commit with metadata changes
Deprecated Properties Removed:
Deprecated fields in 7.15 will affect all Source Node Types regardless of age or activity status. These fields may still appear in our API, but are no longer used in the Node metadata.
dataset
table
metadata.join
metadata.sourceMapping - already absent from most sources
See our previous changelog post about the changes in 7.14.
These features are currently in Private Preview. Please reach out to your Coalesce account manager to sign up.
Coalesce is introducing AI-generated descriptions for Node, Columns, and Git Commit messages.
By analyzing your data pipelines lineage and transformation metadata, it creates natural language descriptions. AI-generated descriptions streamlines documentation by creating clear explanations of data transformations and Git commits. Now you can focus on development while making sure your data pipelines are well documented.
Organization admins can opt-in by going to Organization Settings > Preferences and toggling AI Features.
Run results, Column Headers now support numeric names, ensuring your data displays accurately.
We've temporarily rolled back Workspace Onboarding based on valuable customer feedback. This change was made to ensure the best customer experience possible. We're working on improvements to deliver a refined version in the future. Sign up for our changelog email to keep to date.
We fixed an issue where, when switching tabs in multi-source Nodes the incorrect join string was saved.
Version 7.14.3