fix(core): Handle ghost nodes/connections gracefully #13840
+189
−126
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
There is a bug in the new canvas that doesn't delete all connections when a node is deleted.
This leads to the workflows on the backend that have ghost nodes, which leads to unexpected behavior.
This PR fixes the issue on the backend to handle such workflows that have already been saved to the DB.
We still need to create a fix for the frontend to cleanup connections properly when a node is deleted.
To reproduce the bug
on
master
the execution should fail with an unhandled error, and on this branch, the execution should go through without any issues.Related Linear tickets, Github issues, and Community forum posts
Fixes #13086
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)