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

• Minor internal bugfix to support user onboarding.

On February 11, there were reported issues with our 7.13.1 release. We have fully resolved any issues with version 7.13.2. If you experience any further issues, please contact our support team.

We apologize for any disruption and thank you for your patience.

Follow us at https://status.coalesce.io/ to stay updated on Coalesce system status and any service interruptions.

• Added reliability improvements to the checkout process to ensure first-time success.

• Updated Node deletion to immediately reflect removed nodes in the UI without requiring a page refresh.

Fixed “marked failed errors” during refresh.

We fixed a bug where Nodes with a joinTemplate in their definition did not generate code for the join condition, resulting in the join tab being blank..

• We fixed a bug where deployments fail to proceed past the deploy plan in environments where the initial deploy has failed and no subsequent deployments exist.

• We fixed a bug where the placement of the merge conflict marker (>>>>>>) would invalidate the line of code it was on.

• We fixed a bug where the Results panel would not expand.

• We fixed a bug where if Job names were too long, the Deploy menu would be hidden.

• We fixed a bug where Nodes using joinTemplate didn’t automatically add dependencies.

• We fixed a bug where clicking Validate Select on certain Nodes caused the page to freeze.

• We fixed a bug where missing or corrupted metadata would cause the Mapping Grid to crash.

• We fixed a bug where clicking Discard All in the Git Modal caused a validation error.

• We fixed a bug where package and non-package nodes could lose metadata if a deployment failed without finishing.

Updates

• We’ve made it easier to manage SSO users that have been disabled or deleted.

Bug Fixes

• We resolved an issue in graph execution during deploys where changes to indirectly dependent nodes could result in failed deployments due to incomplete lineage evaluation. The deploy process now accurately accounts for the full dependency lineage of views, ensuring proper ordering of drop and add phases, even when gaps exist in the runtime graph. This fix enhances reliability and reduces the need for redeployments to resolve dependency conflicts.

• We fixed an issue where deploys for advanced deploy node types generated duplicate SQL, causing extra stages to run. SQL is now correctly generated for each stage, improving deployment efficiency and accuracy.

• We fixed an issue where trying to deploy returned an error that Node type does not exist.

This release includes bug fixes and performance improvements.