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

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

• The Git Commits screen now has pagination to make it easier to navigate.

• The Parameters step on the Deploy page now displays correctly.

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.

• Dynamic search works on the Deploy Page.

• Previously credential errors and mismatches would return a 500 for the`startRun` endpoint.`startRun` now returns either a 400 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.

• Fixed issue where changes made to Nodes would not appear in Deploy and Refresh operations.

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

• Minor internal bugfix to support user onboarding.

• New users will now correctly be assigned the correct org role when created.

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.