ZeroLog
Private preview
EN DE

Product

Stopping a Deep Research run now stops it

The Stop button on a research card set the job to stopped, but the run itself kept going in the background and kept calling models. It now ends at the next step.

User impact: Targeted change

If you stop a Deep Research run, it now really stops at the next step and makes no further model calls. No action needed.

A research run is a chain of steps: plan, searches, page reads, extractions, a draft and a review. Until today the run never asked whether you had pressed Stop.

You press Stop CARD Job marked stopped Card shows stopped Nothing else needed Before BACKGROUND Run went on Models still called Report written anyway Now NEXT STEP Checks before each step No new model call Can be resumed later
What Stop does to a research run.
Text version

You press Stop and the card shows the run as stopped. Before, the run went on in the background, still called models and could still write a report. Now it checks before every step, starts no new model call and stays stopped. It can be resumed later from the saved steps.

What changed

Before each new step the run now checks whether it was stopped. A step that is already running finishes, then the run ends. Nothing after that is called or billed.

The same check now also passes through a pause for missing credit. Before, a run without credit treated each refused call as a failed step and kept going with less material.

Prices and plans did not change.

Back to Newsroom

Corrections belong here too. Feed · Docs · X · Legal & privacy