What to Do If the Desktop Keeps Reconnecting After Computer Sleep or Network Switch?
First restore the target machine and network, then trigger desktop connection recovery and check the original task.
Ensure the Execution Machine Is Truly Back Online
Wake the target computer, confirm the network is available, and open Hackcat Desktop. If you are using it from another device, handle it on the executing computer; the current webpage being online does not mean the remote machine has recovered. Do not judge connection status solely by the chat window still showing old output; check the selected computer’s status and the connection under Settings → Remote Control.
Wait for Automatic Recovery or Actively Retry
The desktop will automatically retry some temporary disconnections, with a limit on retry attempts. When the network recovers, the app regains focus, or the page becomes visible, eligible failed connections may attempt recovery; if failure is clear, use the page’s reconnect option. Authentication or connection ownership issues are not always treated as temporary network faults, so repeatedly focusing the page does not guarantee resolution of all failures; check actual error messages.
Verify Execution Status Before Continuing the Task
After the connection is restored, open the original task to check progress and generated results, performing necessary read-only verification first. Commands during sleep may have completed, failed, or be pending; do not assume they will automatically continue seamlessly from the same point. If re-execution is needed, only redo the unfinished parts. CLI connections do not have the exact same desktop recovery process; check if the running terminal is still active before deciding to restart.