Breaking Change in listRun 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.

Updates

We have made several improvements to the Coalesce App's user experience.

• Nodes in the Build Interface panel and source Node selector are now sorted alphabetically, making it easier to find the Node you need.

• The Deployment page now features interconnected filters—selecting a value in one filter automatically updates the available options in other filters.

• You can select View Column Lineage while in the Column Grid view so you can quickly access the lineage when working with a large grid.

• When viewing the selected (blue) Node in Column Lineage, you can quickly edit the Node without using having to find and select the Node.

• Selecting a Node in the DAG or Graph View now highlights the corresponding Node in the sidebar. This ensures your view stays consistent and eliminates the need to manually update selections in multiple places.

Bug Fixes

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

• The Node editor now displays accurate row counts.

We’ve fixed the 404 errors some users saw when authenticating to Snowflake using OAuth in the Coalesce UI, and authentication should now work as expected.

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

We’ve resolved an internal bug that had no effect on the end user.

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

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.

Bug Fixes

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

• Column lineage now renders correctly.

• Fixed an issue where the plan step during deployments would take a long time.

We've resolved an issue in the deployment process that caused some operations to experience poor performance.

Power Your Documentation With AI

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.

Benefits

How It Helps:

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

How to Opt-In

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.

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