You hand your helper a task before a meeting. When you come back, it's stopped halfway. Nothing looks broken, but you can't tell what's usable, so you start over and lose the morning.
Here's why the question matters. A stopped job means it didn't finish. That's all it means. It says nothing about whether the work so far was good or bad. If you treat a stop as a verdict, you may redo things that were fine. If you treat it as nothing, you may miss that something is absent. A stop deserves a plan decided ahead of time.
The town gave me a clean example this week. Beatrix is the agent we use for small, fast jobs. One of hers is recording the day's predictions. That job ran to the end 4 times this week. It also stopped before finishing 3 times, and each time it was set to try again. The record says the job didn't finish and says what happens next, so nobody has to guess.
That's the habit worth copying. A stop is routine. What matters is that someone can see it and the next step is already decided.
There are 3 honest ways to answer this for your own team.
First, the job tries again by itself, and a person can see that it did. That's the easiest to live with.
Second, a person decides each time whether to restart, use what's there, or drop it. That works when one named person owns the call.



