Breaking Change in List Run Endpoint – Version 7.19

Effective in version 7.19, there is a breaking change to the listRun endpoint:

• The orderBy parameter is now mandatory whenever the startingFrom parameter is included in a request. This change ensures consistent and predictable pagination behavior when using the startingFrom cursor.

What you need to do:

• If your integration uses startingFrom, make sure to include a valid orderBy value in the same request. Requests missing the required orderBy parameter will now return an error.

Action Required: Upgrade to CLI v7.17.1

We are notifying all Coalesce customers using command-line tools that an immediate upgrade to the Coalesce CLI version 7.17.1 or higher is required. Snowflake's recent 2025_02 release includes changes that may cause service interruptions for users running older versions of the Coalesce CLI.

To prevent any disruption, please check your CLI version by running:

coa --version 

If your version is lower than 7.17.1, upgrade your CLI by running:

npm upgrade -g @coalescesoftware/coa 

For more information on the Snowflake bundle changes, please visit the Snowflake Release Notes.

Updates

We’ve made several improvements to the Coalesce user experience:

• Nodes in the Build Interface panel and source Node selector are now alphabetically sorted for easier navigation.

• The Deployment page features interconnected filters—selecting a value in one filter automatically updates options in related filters.

• You can now view Column Lineage while in Column Grid view, enabling quick lineage access when working with large graphs.

• When viewing a selected (blue) Node in Column Lineage, you can edit it directly without having to locate and select it again.

• Selecting a Node in the DAG or Graph View now highlights its counterpart in the sidebar, maintaining view consistency and eliminating redundant selections.

Bug Fixes

• Deployments now succeed when a Node's source changes while its name remains unchanged.

• The Node editor now shows an accurate number of Columns that are in a Node.

Packages

Find the right building blocks for your data pipelines and accelerate initial development by using ready-made Packages from Coalesce Marketplace.

New

Delta Stream Merge Node

• Delta Stream Merge Node uses a Delta Stream and handles DELETE operations alongside INSERT and UPDATE.

View-Qualify Advanced Deploy

• View-Qualify advanced deploy UDN is a versatile Node that lets you develop and deploy a Snowflake View with an added QUALIFY filter.

Updates

• Geospatial datatypes are now supported for Dimension Nodes.

• Data quality tests in views now supported in both the Base Nodes package and Base Nodes Advanced Deploy package.

• We've enhanced the InferSchema functionality in Copy Into and Snowpipe Nodes. CSV processing now needs just one file format, not two. The system creates a temporary file format to infer the schema and removes it when the session ends.

Bug Fixes

• A bug in Dimension Zero Key Node related to handling certain edge cases around null value handling has been fixed.

• Persistent Stages change has been made to fix an error caused when all column are chosen as change tracking for Type-2.

We are notifying all Coalesce customers using the command-line tools that an immediate upgrade to the Coalesce CLI version 7.17.1 or higher is required. Snowflake’s recent 2025_02 release includes changes that may cause service interruptions for users running older versions of the Coalesce CLI.

To prevent any disruption, please check your CLI version by running:

coa --version

If your version is lower than 7.17.1, upgrade your CLI by running:

npm upgrade -g @coalescesoftware/coa

For more information on the Snowflake bundle changes, please visit the Snowflake Release Notes.

Thank you for your immediate attention to this matter.

New

Create Node Endpoint

You can now create Nodes using the Create Workspace Node endpoint. Create Workspace Nodes supports creating all Node types. Combined with the Set Node endpoint, create and update Nodes programmatically.

Updates

• We’ve made multiple API updates including:

• Added pagination to List Environments. In addition to existing fields, we have added:

  • total - Number of results

  • startingFrom - The id the request starts from.

  • limit - The request page size. 100 is the default.

  • next - The value where the next page of results starts after.

• Added type to List Run Results. Type indicates if it is a sql or sqlTest run.

• When using ref functions, an error message will return if there is a cyclical dependency.

• We’ve made some user interface improvements including:

• Added tooltips for all statuses in the Activity Feed.

• The Fetch button in the Git Modal has moved to be in-line with commit and branches.

• Improved Column Lineage so it's easier to see the Node lineage.

Packages

New - View-Qualify Advanced Deploy Node

We’ve released a new package Node, View-Qualify Advanced Deploy UDN. This is a versatile Node that allows you to create and deploy views in Snowflake using the QUALIFY filter. It gives you a streamlined way to filter records within a View using window functions such as, RANK or ROW_NUMBER. It supports common use cases like deduplicating data, selecting top and bottom records, and applying customer filters.

Bug Fixes

• Clicking on a Node in the Docs no longer results in an error screen.

7.17.1

Node and Column Test Failures

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.

Updates

• 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.

Bug Fixes

• 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

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:

1. Making a commit with the changes.

2. 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.