Subscribe to updatesOn 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.
Version 7.13.1
Setting up Workspaces in Coalesce just got easier. Our new Workspace onboarding guides you through the processes step-by-step reducing configuration time. Workspace onboarding makes it easier to set up version control, authentication, and Storage Locations/Mappings. This means less setup time and more focus on building pipelines.
Our Hash editor automatically displays all columns with proper scrolling functionality.
Problem Scanner can detect and alert on duplicate Node names and Storage Mappings, making it easier to find potential problems.
We've made several improvements to enhance platform speed and reliability. These changes are part of our ongoing commitment to deliver the best possible experience for our users.
Source filters now correctly populates and displays all available results.
Fixed an issue where, “A write batch can no longer be used after commit() has been called.”, was returning when trying to checkout branches.
Node column details in the lower-left corner now consistently display when clicking Nodes.
Node Editor scrolls correctly when the “Node not enabled for deploy” banner is displayed.
Coalesce will be taking a scheduled maintenance window. During this time, search functionality within the generated documentation pages will be temporarily unavailable.
Maintenance Details:
• Date: Monday, February 17, 2025
• Time: 8:00 PM - 10:00 PM US/Pacific
We are performing this maintenance to enhance the stability and performance of our platform. We expect search services to be fully restored by 10:00 PM PST, but will notify users if there are any delays or updates.
The rest of the platform will remain fully operational during this time.
We appreciate your understanding and apologize for any inconvenience this may cause. If you have any questions or concerns, please feel free to reach out to our support team.
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.
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.
You can now add a "Re-Sync Columns" button to custom Nodes. This feature allows users to sync columns that are not part of a source Node. Learn more in Custom Node Types.
We’ve made updates to product feature speed.
We’ve made it easier to manage SSO users that have been disabled or deleted.
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.