Assets & tasks / PRODUCTION GUIDE
Does stopping a product batch cancel the item already generating?
Stopping a batch prevents its waiting items from starting. It does not cancel an item that already has a submitted generation job, delete completed results or prove a refund. Inspect the current job separately and let its recorded outcome guide what you keep, recover or plan next.
Separate queue control from the submitted operation
In a hypothetical mug campaign, one blue-mug image has completed, a green-mug image is currently generating and a white-mug image remains waiting. The merchant decides the remaining creative direction is wrong. Stop remaining tasks is useful for preventing the white-mug request from starting. It should not be read as an instruction that recalls the already submitted green-mug operation from the provider.
Read the item list before stopping so you can describe what is actually underway. A batch waiting entry has not reached the same stage as a submitted job. Do not infer that a task is unstarted merely because its preview is empty. Check Generation tasks for the current job identity and recorded state, particularly if the browser was disconnected during submission.
Understand the effect on each kind of item
| Item before Stop | Expected batch effect | Follow-up |
|---|---|---|
| Waiting with no submitted job | Cancelled in the stopped queue | Include it in any later revised plan |
| Already generating | Job is not cancelled by this action | Inspect its independent task outcome |
| Succeeded | Existing result is retained | Review and download if useful |
| Pending or unknown submission | Outcome is not established by Stop | Resolve the original task state |
The current queue marks waiting entries cancelled and changes the batch to stopped. Items with existing jobs continue to reflect the job outcome when status is refreshed. In the mug example, the green-mug result can still arrive later. That result should receive an ordinary product review; stopping the queue does not automatically make it rejected, deleted or unavailable.
Use Stop when the remaining plan no longer makes sense
Choose this action when you want to prevent further items using the saved batch plan. A wrong product edition, unsuitable scene direction or changed campaign requirement can justify that choice. Keep a short explanation so another reviewer understands why the remaining entries were stopped. Do not stop merely to create a second overlapping batch when the original job is still unresolved.
A stopped batch is different from a paused batch awaiting valid continuation. The current Continue action applies to paused batches; it is not a general restart button for stopped work. If the remaining products need a revised plan, prepare a new batch after reviewing the original job and quote. Preserve useful completed results rather than treating the old batch as disposable history.
Different creative operations can consume different generation allowances.
Review the current job and credit record independently
Open the recorded generation for the green mug. If it succeeds, compare the actual product and decide whether that asset serves any valid placement. If it fails, read the shown outcome and credit records. If its submission remains uncertain, use the available original-task recovery path. Stopping the queue does not establish which of these outcomes occurred or whether the provider already incurred processing work.
Do not promise a refund for a submitted operation simply because the campaign changed. The batch action is a queue decision; billing follows the particular generation record and applicable account rules. A full planned batch quote is also not evidence that every waiting entry was already charged. Check actual records rather than multiplying cancelled entries by a remembered tutorial price.
Abandoning an uncertain job, where that action is available, is a separate decision with its own displayed consequence. Do not use the word stop to describe both operations without explaining the difference. Preserve the original task identifier for reconciliation and avoid creating a replacement solely because the stopped batch no longer advances.
Build the replacement set from accepted results
After the current mug job reaches a clear outcome, decide which campaign assets remain usable. The blue-mug image may still meet the brief, and the green-mug image may be acceptable even though the saved scene direction was discontinued. List only the missing or wrong deliverables in the new plan. This keeps the revised production scope tied to actual needs rather than recreating every old item for administrative neatness.
Use task-state investigation before replacing uncertain work. Consult variant-level approval when deciding which completed results remain approved. Keep the stopped batch, original job outcome and replacement plan distinguishable in your notes. None of those records should claim provider cancellation or payment reversal unless the actual operation and account evidence establish it.
Sources and further reading
Sources for this page were checked on . Platform rules can change; verify the current source before publishing. Prompt examples and workflow recommendations are Itemlume editorial guidance, not independently measured results.
Frequently asked questions
Can the current image finish after I stop the batch?
Yes. Stop remaining tasks does not cancel a generation job already submitted; inspect that task separately.
Can I resume a stopped batch with Continue?
The current Continue action applies to paused batches. Plan revised remaining work separately after resolving existing jobs.
Does Stop automatically refund a running operation?
No refund is established by this queue action. Use the recorded job outcome and account credit records.
BUILD FROM A PRODUCT YOU KNOW
Put this workflow into practice with your own product.
Explore the relevant tool first. AI copy and concept planning are free after sign-in. Image and video generation require available credits and the applicable account access.
Open Assets & tasks Check pricing and credits