Case study
Why an AI tool stop button still running costs you
An AI tool's Stop button often stops only the visible part of the job, while queued and late work carries on being paid for. We traced why in a tool we built for a client, and what a real stop has to do.
Key takeaways
- A Stop button is only as good as the places it reaches.
- Recording the moment of a cancel is what lets late work be told apart from work someone asked for afterwards.
- An automatic mode can start the next step after a stop, so switch it off before you cancel.
- A request already sent to a paid AI service may still be charged even when its result is thrown away.
- Finished pieces should survive a cancel so a render can begin from where it stopped.
The client now has one Cancel button, and pressing it stops an ad everywhere it is being worked on. The change was live after about a day of design, building and review, and it removed the problem of an AI tool stop button still running the rest of the job. Before it, pressing Stop stopped only the part of the work the people using it could see.
What an AI tool stop button still running means for your bill
An ad made with AI is not one job but many, and every step that carries on after Stop is spent on a result nobody wants.
A video ad is split into pieces: pictures being drawn, single lines of script remade, voice changes and the final render that puts them together. Each piece calls a paid AI service, paid for by use, so a stop that reaches only one piece leaves the rest running and charging.
It also takes capacity from the ads that are wanted. And a late result can write into a cancelled ad, bringing back to life a decision that had already been made.
Why this happens to businesses that use AI tools
Stop is usually built for one kind of work, while an ad is many kinds of work in many places at once.
A tool that makes images, voice and video rarely does all of it in one place. It hands each piece to another part of itself or to an outside service, and each has its own queue and its own way of reporting back. The button on screen often talks to one of them.
Two gaps make it worse. Nothing records the moment of the stop, so work already waiting or arriving late cannot be recognised as unwanted. And an automatic mode, the setting that starts the next step by itself, can do exactly that after a Stop.
What our engineers found when they traced it
Our engineers started by listing everything that can be under way for one ad at the same moment, and found more than a dozen kinds of work.
Those sit in different places: the platform itself, the engine that plans and makes clips, the accounts that produce AI video clips, and the separate machines that render the final video. Following one ad's work across all of them explained what the people using it were seeing.
A job already waiting in a queue could start a minute after the stop. A machine that had been down could finish a render later and send it back. A result arriving late could mark the ad as working again. And because someone could press Start a second after pressing Stop, the system had to tell work asked for before the stop from work asked for after it.
That was not the end of it. The first version went through six rounds of review, and each round found a narrower case where two things happening at the same instant could still slip through.
What we changed
The client now has one Cancel button, and pressing it stops the ad everywhere it is being worked on.
It can be pressed for one ad or for several at once. Pressing it switches the automatic mode off first, records the exact moment of the cancel, then fails every step under way for that ad and tells every part involved at once to drop the ad's work that started before that moment.
Three details do most of the work:
- Jobs still waiting in a queue from before the cancel are dropped without running.
- Results that arrive late are thrown away instead of being written into the ad.
- Machines that were down are told again a few minutes later, so one coming back does not quietly finish an old job.
Afterwards, nothing on that ad starts by itself. It waits until someone presses Start, Render or the automatic mode again. Everything already made is kept, so a render can start again from what exists rather than from nothing.
The confirmation says one honest thing: a request already sent to an AI service still finishes and may be paid, but what comes back is not used.
Where it stands now
The change is live in the tool the client uses. One press stops an ad everywhere it is being worked on, nothing restarts on its own, and the spending stops with it apart from calls already on their way.
A short guide for the people who use it explains how it works.
What you can check yourself
- Press Stop in your AI tool and watch the costs page for a while afterwards. If the figure keeps climbing, something is still running.
- Ask your supplier what happens to a job already waiting in a queue when you press Stop. "It is dropped" and "it runs anyway" are very different answers.
- Look for an automatic or scheduled mode and see whether it can start the next step after a stop. Switch it off before you cancel, not after.
- Ask whether a result that arrives late can overwrite a decision someone made after they asked for it.
- Ask what happens to a request already on its way to a paid AI service, since that is the part no button can recall.
What to do next
If you pay for AI work by use, the useful question about any tool is not whether it has a Stop button but what that button reaches. Ask it of the tool itself, of whoever set it up for you, and of anyone whose people share the account. Then write the answer down, because it is the sort of thing everyone assumes until the costs page says otherwise.
Making Stop mean stop, across every part of a tool that hands work to other parts and to paid services, is the kind of job our engineers do for clients.
Questions people ask
Why does my AI tool keep charging after I press Stop?
Because Stop often reaches only the part of the tool that shows progress. The rest of the job may be waiting in a queue or already sent to a paid AI service, and those parts can continue and be charged. Watching the costs page after a stop is the quickest way to see whether that is happening.
What happens to a job already waiting in a queue when I cancel?
Ask your supplier to say it plainly, because it varies by tool. A queued job can still start when its turn comes unless the tool was built to drop work queued before the cancel. If the answer is not clear, treat the job as still live until the costs page stops moving.
Can an automatic mode restart work I cancelled?
An automatic or scheduled mode can start the next step by itself, and it does not know that someone pressed Stop a moment earlier. Switch it off before you cancel, and ask whether the stop does that for you. If it does not, the job may restart without anyone asking.
Can I get back the money for an AI request that was already sent?
Once a request reaches a paid AI service, it finishes and may be paid; no button can recall it. A tool can refuse the result, so what comes back is not used, but the call itself remains. Ask your supplier whether they pass that charge on.
Will I lose the parts of the ad that were already made if I cancel?
A tool built for cancellation should keep every finished piece. That lets someone press Render again and start from what exists rather than from nothing. Ask your supplier to confirm that cancelling does not delete completed work.