Pause a DecisionBox run and pick it up where it stopped
Since v0.38, a DecisionBox discovery run saves its work as it goes. If a run is interrupted, it resumes where it stopped instead of starting again from the first query. You can also pause a run yourself, give the warehouse back to your team for a while, and resume it later without losing what it has already done.
What a discovery run costs you
In a discovery run, DecisionBox explores your warehouse on its own, then checks what it found and turns it into recommendations. The how it works page shows each stage, and the AI agents page shows who does what.
That takes time and it takes money. The first discovery guide says to expect roughly 30 minutes to a couple of hours for a run with the default 100 exploration steps. A first run on the public e-commerce demo data took about 52 minutes. All that time, the run is spending on two things: queries on your warehouse and calls to the language model.
The v0.38.0 release notes are clear about where most of that goes: "Exploration is where almost all of a run's cost sits."
Why interrupted runs mattered
Long jobs get interrupted. The release notes list the usual causes: a connection that times out, a server that gets moved or restarted, a process that runs out of memory.
Until v0.38, an interrupted run was simply lost. Everything it had paid for was gone, and the only way forward was to run it again from the first query. Starting again meant paying to repeat work the run had already finished, and the later the interruption, the more work that was.
There was also only one way to stop a run early: Cancel. Cancel throws the work away. So if your team needed the warehouse back in the middle of a run, the choice was to wait or to start over later.
What changed in v0.38
A run now keeps a record of its finished work as it goes. When an interrupted run resumes, DecisionBox picks up from that record:
| Stage of the run | What happens on resume |
|---|---|
| Exploration | restored in full: the queries already run on your warehouse are not run again |
| Analysis | the run analyzes your data one subject (area) at a time; finished areas are kept and only the remaining ones are analyzed |
| Checking findings | in a subject the run was still checking, only the unchecked findings are checked; its analysis isn't redone |
| Recommendations | written once; only the ones not yet checked are checked |
The release notes give an example: a run that stopped after checking 4 of the 6 findings in one area now pays for the remaining 2, and it doesn't repeat the analysis behind them either.
Pause: stop now, carry on later
Pause is the new way to stop a run without losing it. The run finishes the step it is working on, saves it, and waits in a paused state until someone resumes it. In the words of the release notes, you can use it "to give the warehouse back, or to stop the clock, without throwing away what you have already paid for."
If the warehouse is busy, pause and come back when it's quiet. If someone needs to look at the setup before the run goes further, pause and resume once they have.
Cancel still exists and still means "discard this run". It now asks you to confirm, and says exactly that.
What it doesn't do
Pause waits for the current step to finish, so a run doesn't stop at once. Close to the end, while a run is saving its results, it can't be paused, because it is seconds from finishing. In that case the request is refused and says why, so nobody is left waiting for a pause that won't come.
Resume can only reuse work a run had finished and saved. A step that was halfway through when the run stopped is done again.
A cleaner record of every finding
The same release fixed how DecisionBox records its queries. When DecisionBox ran a corrected version of a query that had failed, the record used to keep the first attempt, even though the numbers came from the corrected one. Now each step records the query that actually ran.
That matters because those queries are the evidence behind a finding. The AI agent that checks findings reads them, and so do you when you open a finding to see where its numbers came from. Our post on how DecisionBox checks a finding and the validation page explain those checks.
Where to find it
Saving work during a run and resuming it are part of v0.38.0, in both the open-source Community edition and Enterprise. A run in progress shows Pause next to Cancel, and a paused run shows Resume from step N. The v0.38.0 release notes have the full details.
To try it on your own data, start with the self-host guide.
