Skip to content

Error Failed to save workflow draft #14357

Open

Description

@cor-of-org

Custom Node Testing

Expected Behavior

Nothing at all.

I did not expect to be interrupted, nor be forced to pick up my mouse and click a pointless button which I did not even ask for.
I expected nothing to happen other than the things I was doing, or rather trying to do. I expected only my actions to be happening.

Actual Behavior

A stupid, pointless pop-up informing of something that I did not request not happening. If it happened once, on April 1st, I would laugh, but it happens dozens of times a day and is pissing me off.

And it doesn't just happen once, nope. Again and again and again on the same tab saying the same thing; "I cannot save something you have not asked me to save".

I have searched the preferences and I can't find a preference for me to choose to disable saving a "workflow draft", which sounds like a useful feature but if it means interrupting me every two fucking minutes I would disable immediately and that's exactly what it's doing and I didn't even ask for it.

Steps to Reproduce

I click on a tab from yesterday and do anything. Anything at all. Edit text, move a node, anything.

Debug Logs

All good here!
[INFO] 0 models unloaded.
[INFO] Model AutoencodingEngine prepared for dynamic VRAM loading. 159MB Staged. 0 patches attached. Force pre-loaded 108 weights: 182 KB.

Other

No response

Activity

  1. hbomb-dev commented on Jul 5, 2026

    @hbomb-dev

    you've worked with devs before haven't you? you know just how to get in their good books...

  2. cor-of-org commented on Jul 7, 2026

    @cor-of-org
    Author

    Real devs, sure. These fucking amateurs, no, you're right, not so much.

  3. xmarre commented on Aug 7, 2026

    @xmarre

    I tracked the repeated Failed to save workflow draft path down in the current frontend and opened Comfy-Org/ComfyUI_frontend#14897.

    The V2 quota-recovery path can permanently enter this failure loop after a localStorage quota failure: it deletes older LRU draft payloads while trying to make room, then if the incoming draft still cannot be fully committed it leaves those previous payloads gone and calls a one-way markStorageUnavailable() latch. From that point every later autosave returns false until reload, which is why the same notification can appear on every edit.

    #14897 makes failed saves data-preserving and retryable, rolls quota evictions back if the incoming draft cannot commit, preserves the workspace-transition write fence, and limits the notification to one per continuous failure episode. The focused persistence suite passes 72 tests plus lint, typecheck, and production build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Potential BugUser is reporting a bug. This should be tested.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions