An Interrupted Run Picks Up Where It Was ​

September 7, 2026 · InfraScout Team

A scheduled assessment can run for the better part of an hour, and much of what it does cannot be repeated for free — tool calls that reached real hosts, AI turns you were charged for. A single momentary fault anywhere in that run used to end it and throw all of that away.

Three changes make long-running work survive the interruptions it will inevitably meet.

A scheduled run continues instead of ending ​

A run that meets a brief interruption now waits it out and carries on, rather than failing and discarding everything it had already produced.

That is safe because of how a run records its progress: each record is written so that repeating it cannot duplicate anything or overwrite a later result. The wait is comfortably longer than the interruptions we see in practice, so a run that would previously have been abandoned at minute eight now reaches its summary.

The "Reconnecting" banner clears itself ​

A chat turn is deliberately detached from your browser tab, so closing the tab does not stop the assessment — that is by design. The cost of it was a tab that could sit on "Reconnecting — the assistant is still working" indefinitely, waiting for news that was never coming. The conversation looked wedged when it had simply finished.

A turn interrupted by a planned restart is now wound up properly: the partial answer is saved and your tab hears about it within seconds. Where the interruption was not planned, a tab showing that banner re-checks on its own every half minute, so it clears itself either way.

There is an honest trade behind that. Recovering a turn that genuinely has stopped now takes closer to ten minutes than two, because a long tool phase against a real fleet can outlast any shorter window you would pick. If you are looking at a turn you believe is dead, give it the ten minutes. Waiting costs you nothing; assuming work has stopped when it has not costs you a duplicate run against the same hosts.

Steering reaches a live turn, or becomes a message ​

Text typed under a stale banner used to be accepted as steering for a turn that had already stopped, then discarded at the next turn. It looked delivered and was not.

Steering now requires a genuinely live turn. Where there is none, what you typed is sent as an ordinary message rather than vanishing.


More detail: Chat — when a turn fails, or your connection drops.

Questions or feedback? Reach us at info@infrascout.cloud.