Queue Next:
QueueNext_BFT automatically submits another run of the current ComfyUI workflow after this node executes, making it useful for processing a folder of images or videos one item at a time. Place it at the end of the processing path and start the workflow once; each completed run can then queue the next one. With the supported folder loaders, processing stops when the loader has no more items, because the loader fails before QueueNext_BFT runs again. The node also adjusts certain values in the resubmitted workflow to help prevent caching from skipping a run or reusing a stale result.
Queue Next Input Parameters:
image
An optional IMAGE connection. Connect the final image from your processing chain here when you want QueueNext_BFT to run after that image-producing step. The node does not modify or inspect the image; the connection establishes where this node sits in the workflow’s execution path. There is no numeric minimum or maximum, and the source defines no image default; when unconnected, the node receives None.
text
An optional STRING connection. Connect the final text from your processing chain here when you want QueueNext_BFT to run after that text-producing step. This is a connection-only input, so it is intended to receive another node’s text output rather than text typed into a widget. The node does not modify or inspect the text. There is no length limit, option list, or text default specified in the source; when unconnected, the node receives None.
Queue Next Output Parameters:
There are no output sockets. QueueNext_BFT acts as an endpoint that schedules another workflow run; it does not produce an image, text, or other value for a downstream node.
Queue Next Usage Tips:
- Connect the final IMAGE or STRING result of the processing path you want to finish before the next run is queued. You do not need to connect both inputs.
- Use it with FolderImageLoader_BFT or FolderVideoLoader_BFT when processing a folder sequentially. Start with one Queue Prompt action; the node queues subsequent runs after it executes.
- Keep any save or export step in the processing path before QueueNext_BFT, so the next run is not queued before that step completes.
- In sequential folder-loader workflows, the requeue helper increments the loader’s
indexvalue to help avoid prompt-level deduplication. The supplied context says that value is ignored by the loader in sequential mode, so changing it is not a way to choose the next item. - If the workflow includes an AILab_QwenVL or AILab_QwenVL_Advanced node, the requeue helper changes its
seedon the submitted prompt to help avoid stale internally cached results.
Queue Next Common Errors and Solutions:
[BatchFolder] Re-queue failed: <error details>
- Explanation: This is the error prefix printed when the background attempt to submit the next workflow run fails. The details after the colon vary with the cause. The provided code submits to
http://127.0.0.1:8188/prompt, so an unavailable server or a server using another address or port can prevent the next run from being queued. - Solution: Check the ComfyUI console for the full error details. Confirm ComfyUI is running and that its prompt endpoint is reachable at the address and port used by this installation; if your setup uses a different address or port, the helper’s configured endpoint needs to match it.
Folder loader reports that no items remain
- Explanation: The exact loader error text is not included in the provided source. When a supported folder loader runs out of items, it fails before QueueNext_BFT executes. No further run is queued; this is the described stopping behavior, not necessarily a fault in QueueNext_BFT.
- Solution: If the folder is complete, no action is needed. If you expected more items, check the loader’s folder and its selection settings before starting another run.
No next run appears, with no re-queue error
- Explanation: QueueNext_BFT queues another run only when it executes and receives the workflow prompt. The supplied source does not establish a specific error message for a disconnected processing path or an earlier node failure.
- Solution: Check whether QueueNext_BFT ran, connect your final IMAGE or STRING result to it, and resolve any earlier workflow error shown in ComfyUI.
