You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Errors from another workflow may persist after switching to a drag-dropped API workflow #14656
An API-format workflow opened by dragging and dropping the JSON onto the canvas appeared to keep showing a different workflow's errors after switching tabs into it — i.e. the incoming tab did not clear the outgoing workflow's error state.
Filing so it is not lost. I could not reproduce it, and the original observation was made on a branch that no longer exists, so the symptom may be stale.
What was tested
On a local tree with #14555 and #14557 merged, two workflow tabs were created, each with a different uninstalled node type, and the error panel and overlay were read at each step:
step
panel
overlay
tab-alpha active
Unknown pack MissingNodeAlpha
Missing node: MissingNodeAlpha
tab-beta active
—
Missing node: MissingNodeBeta
switched back to tab-alpha
—
none
No leakage: while tab-beta was active, nothing from tab-alpha was shown. The reported pollution did not occur.
The absent overlay in the last row is by design — tab switching calls showPendingWarnings(undefined, { silent: true }) from workflowService.openWorkflow, and silent suppresses showErrorOverlay() while still syncing the store.
What was NOT covered
The drag-and-drop entry path. The test drove window.app.loadApiJson(...) directly rather than dropping a file, so anything specific to the drop handler (deferWarnings: true for each file, then a single showPendingWarnings() after the loop) is untested here.
The original branch the symptom was seen on. It was a pre-restructure version of the errors work that was discarded, so the behaviour there is not recoverable.
Repro steps to try
Open a workflow that reports an error (missing node or missing model).
Drag and drop an API-format JSON referencing an uninstalled node type onto the canvas.
Switch between the two tabs and watch the Errors panel.
Activity
coderabbitai commentedon Aug 4, 2026
🔗 Related PRs
#14246 - Naq gura gurer jrer abar [open]
#14251 - fix: keep missing node packs across runs [open]
#14290 - fix: isolate and preserve workflow drafts on workspace switch [merged]
#14555 - fix(workflow): build nodes for uninstalled types on API JSON import [open]
#14575 - fix: persist workflow drafts across page refresh [open]
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!