In ComfyUI, Clear queue cancels jobs that are queued but have not started; Clear history removes entries from the job history list. They act on different things. Neither list changing, by itself, proves that a completed output stored in Assets or elsewhere was deleted. Before clearing history, read the confirmation dialog’s note about stored assets on your installation.
Identify what you want to change
Think of three separate objects: pending jobs waiting to run, records of past jobs, and output assets from completed jobs. A queued job is not yet running. A history entry is a record you can browse and, depending on its status, use for actions such as opening its workflow. A completed job’s preview or output may also appear in Assets when the assets system is enabled.
The Job History panel is available as a docked sidebar when Comfy.Queue.QPOV2 is enabled; otherwise, the floating job-history overlay remains available. The documented queue and history controls belong to that job-history surface. ComfyUI’s Job History documentation describes the panel and its actions.
Choose an action from the job state
Before acting, check the status shown for the specific work you care about. The panel distinguishes queued and running work from completed and failed runs. Clear queue applies to all pending jobs, not only a selected row, so first confirm that none of the queued jobs should be kept. A running job is not a pending job and is not what the documented Clear queue control cancels; use the job’s Cancel action if you mean to stop a particular running job.
Use Clear history when the goal is to clear entries from the job history list. It opens a confirmation dialog. Stop and read the dialog’s note about stored assets before confirming: the documentation does not specify a universal asset-deletion result for every installation. The documented history actions distinguish clearing the history list from actions on individual jobs, such as inspecting or downloading a preview asset.
Clear the intended list
- Open the Job History sidebar or floating job-history overlay. If the docked tab is missing, check whether Docked job history/queue panel (
Comfy.Queue.QPOV2) is enabled in Settings under Comfy → Queue → Layout. - Inspect the status summary and job rows to distinguish queued, running, and past runs. Before using Clear queue, check the entire queue for jobs that should be kept: the control cancels all pending jobs as a whole, not just a selected row.
- For pending work, activate Clear queue and use the status or feedback actually provided by the panel to determine whether those jobs were cancelled. For a specific running job, use its Cancel action instead. The documentation does not specify how cancelled jobs will subsequently appear in history, so treat any history check as an independent observation rather than a required result.
- To clear job history entries, open the header actions menu and select Clear history. Read the confirmation dialog, especially its note about stored assets on your installation, before choosing whether to proceed.
- After confirming, inspect the list and, separately, Assets if you need to check whether a completed output remains available. Verify the object you intended to change rather than relying on a single disappearing row.
Check the result without overclaiming
The following is a hypothetical example of what to check, not a report of a software test. Suppose the panel shows two queued jobs, one running job, and four completed records. A useful acceptance check is:
| Intended action | Before: hypothetical observation | Check after the action | What the check establishes |
|---|---|---|---|
| Clear queue | 2 queued, 1 running | Use the panel's actual status or feedback to confirm whether the two pending jobs were cancelled; check history separately only if needed | The pending jobs were acted on; the documentation does not specify how they will subsequently appear in history, and this does not establish that outputs were deleted |
| Clear history | 4 history entries | History entries are no longer listed; inspect Assets separately if relevant | The history list changed; list disappearance alone does not establish asset deletion |
If an entry appears different from what you expected, first check whether you are viewing the intended workflow filter or status view. The panel can filter between All workflows and Current workflow, and between status tabs such as All and Completed. If a running job remains after clearing the queue, use that row's Cancel action if you need to stop it.
Limits and common questions
Does Clear queue remove completed jobs from history? Its documented scope is pending, not-yet-running jobs. The documentation does not specify how cancelled jobs will subsequently appear in history; use Clear history when the goal is to remove queue-history entries.
Does Clear history delete generated images? Do not assume so. Clear history removes queue history entries, while the confirmation dialog contains the relevant note about how that relates to stored assets on your installation. Check that note and inspect Assets separately if you need to establish whether an output remains available.
Can I use Clear queue to stop a running job? The documented control cancels pending jobs. For one running job, use that row’s Cancel action. Check the resulting status in the panel; do not infer that a cancellation also clears the job’s history record.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.