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
every operation triggers a "Failed to save workflow draft" error. This error persists even after manually disabling "Show error tab in side panel" in Settings > Error System. #13131
I have tried disabling custom nodes and the issue persists (see how to disable custom nodes if you need help)
Expected Behavior
I hope to have the option "whether to forcibly save the workflow draft after every operation" as a toggle in the settings that can be manually turned on or off. When this setting is turned off, it should still be possible to manually save the workflow draft, and a pop-up should appear when closing the entire web page, asking whether to save the workflow.
Actual Behavior
Every operation (whether dragging the workflow, generating an image, or any other action) triggers a "Failed to save workflow draft" error. This error persists even after manually disabling "Show error tab in side panel" in Settings > Error System.
Steps to Reproduce
After entering ComfyUI, navigating to Workflow, clicking a saved workflow file, and making any changes (such as running the workflow, enabling nodes, creating groups, etc.), an error occurs.
Debug Logs
There is no error reported in the terminal.
Other
No response
Reacted by DarkSouljah, GHOSTLXH, YUMERIA, Djanghost, heresyCoder, Metam0rfosen, Mark Cockram and Robert Waters
I was experiencing the same issue in Chrome - and, this cleared it:
The "Failed to save workflow draft" error in ComfyUI is typically caused by a known browser storage bug or an outdated frontend version.
Clear Browser Local Storage: This is the most common fix. Open your browser's developer console (F12), go to the Console tab, and run the following command: localStorage.removeItem('Comfy.Workflow.Drafts')
Then refresh the page.
Hard Refresh: Press Ctrl + F5 (or Cmd + Shift + R on Mac) to bypass the browser cache and reload the interface.
Reacted by Han, svyatojdismas, Metam0rfosen, Carlos, Andy House, Ozzimi, Mark Cockram and Jeffisnothere
The important failure is in V2 draft quota recovery: once a draft payload write hits localStorage quota, the store starts deleting older LRU draft payloads before it knows the incoming draft can be committed. If the incoming payload/final index still fails, those old payloads are already gone. The same path then calls a one-way markStorageUnavailable() latch, so every later autosave returns false for the rest of the page lifetime and produces the repeated Failed to save workflow draft behavior.
On restart, index/payload drift cleanup removes entries whose payloads were deleted, which explains reports where draft history subsequently appears to vanish.
#14897 makes failed saves non-destructive, keeps quota failures retryable, rolls tentative evictions back on all failure paths, preserves the newer workspace-transition write fence, and deduplicates the error notification per continuous failure episode. The focused persistence suite passes 72 tests plus lint, typecheck, and production build.
I would strongly avoid recommending localStorage.clear() as a first-line workaround here: it destroys any draft data that is still recoverable.
Activity
huanggou666 commentedon Apr 3, 2026
解决了吗 ,好多天了 一直弹
huanggou666 commentedon Apr 3, 2026
Failed to save workflow draft
clink2012 commentedon Apr 3, 2026
I was experiencing the same issue in Chrome - and, this cleared it:
The "Failed to save workflow draft" error in ComfyUI is typically caused by a known browser storage bug or an outdated frontend version.
simsim9-stack commentedon Apr 27, 2026
А как тоже самое сделать в firefox?
localStorage.removeItem('Comfy.Workflow.Drafts')
возвращает
undefined
Metam0rfosen commentedon May 16, 2026
Same error here, very annoying.
xmarre commentedon Aug 7, 2026
I tracked this failure path down in the current frontend and opened Comfy-Org/ComfyUI_frontend#14897.
The important failure is in V2 draft quota recovery: once a draft payload write hits localStorage quota, the store starts deleting older LRU draft payloads before it knows the incoming draft can be committed. If the incoming payload/final index still fails, those old payloads are already gone. The same path then calls a one-way
markStorageUnavailable()latch, so every later autosave returns false for the rest of the page lifetime and produces the repeatedFailed to save workflow draftbehavior.On restart, index/payload drift cleanup removes entries whose payloads were deleted, which explains reports where draft history subsequently appears to vanish.
#14897 makes failed saves non-destructive, keeps quota failures retryable, rolls tentative evictions back on all failure paths, preserves the newer workspace-transition write fence, and deduplicates the error notification per continuous failure episode. The focused persistence suite passes 72 tests plus lint, typecheck, and production build.
I would strongly avoid recommending
localStorage.clear()as a first-line workaround here: it destroys any draft data that is still recoverable.fix(persistence): tolerate index desync and report quota exhaustion i…