Define who owns the process
The browser, terminal client and server process have separate lifecycles. Specify whether closing the session ends the process, detaches it or leaves a managed job available. A reconnect button alone cannot guarantee continuity.
Retain the job identifier, start time, current state and last confirmed output. An operator can inspect the existing work before starting another copy.
Handle an unknown result carefully
A lost response may follow a completed operation. Repeating a file write or deployment without checking can duplicate work. Use a status lookup or operation reference for actions that cannot safely repeat.
Reading a status and changing a configuration can have different retry policies. The interface should explain what is known about the previous attempt.
Rehearse interruption
Test a dropped connection, full output buffer, terminated process and service restart. Verify what can resume, what must restart and what requires review.
Interactive sessions need output continuation. Scheduled jobs need results that remain available after the initiating page closes.
Before you begin
Can output be retrieved after a timeout?
Where the session service retains it, yes. Its retention and expiry policy form part of the design.
Should a failed command always retry?
No. The outcome and repeatability of the action determine whether a retry is appropriate.
DSDillon / 26 September 2026
