AsyncOutput[module_config] Global Memory Reset

AsyncOutput[module_config] Global Memory Reset (class AsyncOutputGlobalManualReset) is the manual flush button for every bit of state the AsyncOutput pack holds. Where the Global Auto Reset node decides whether the pack forgets automatically at the start of each run, this one clears everything right now, on demand - the collection storage, the counters, the multiline-yield indexes, the remote-control data, all of it, in one shot.

You'll want it in two situations. First, debugging: the pack's state lives in Python process memory and it's invisible, so when a loop starts behaving like it remembers runs that never happened, a manual reset gives you a clean slate without restarting ComfyUI. Second, as the explicit cleanup step when you've turned auto-reset off - if state is surviving across runs by design, this is your controlled way to end the streak.

How it works

The node's manual_reset function replaces all the module globals (ASYNC_OUTPUT_STORAGE_DATA, ASYNC_OUTPUT_COUNTER, the multiline-yield dicts, the remote-control dicts) with fresh empty dictionaries, then prints a status line to the server console showing whether auto-reset is currently enabled. Its output, reset result (BOOLEAN), echoes back the boolean you passed in.

The inputs that matter

• reset_all_memory (BOOLEAN, default false) - the trigger. The wipe happens regardless of true or false, because both branches empty the dicts. This is the input that matters, and its default is a trap, see below.

Installing it

Zero dependencies, no model downloads - standard for this pack. ComfyUI Manager → search "AsyncOutput" → install and restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/teddy1565/ComfyUI-AsyncOutput

It's under AsyncOutput/Deprecated(ComfyUI NOT Turing complete)/Global/ManualOperation.

Where people get burned

Two things. First, the counter-intuitive bit: the wipe fires whether you pass true or false. The boolean's real job is setting the global auto-reset flag - pass true and you've cleared memory and re-enabled auto-reset; pass false and you've cleared memory and disabled auto-reset. If you wire this to a toggle that's false most of the time and expect it to be inert, you're wrong - it wipes every time it executes. Only place it where you genuinely want a reset.

Second, this is a process-global action. There's no workflow scoping - one graph's manual reset nukes the state for every AsyncOutput graph running in the same ComfyUI process. Fine for a single-user box, a footgun if you're running multiple workflows side by side and expecting them not to interfere.