When a computer is offline
A computer Project runs commands on the paired computer, not on the Elowen server. If the computer is offline, a command fails rather than switching to another machine. If a connection drops after a command was sent, its outcome may be unknown; check the computer before repeating a change.
Check the computer's status
- Open Account → Computers to see whether the computer is connected and when it was last online.
- Select its Project and check its last-online time and client information.
- If a command was already sent, inspect its conversation output and check the computer directly before retrying it.
The computer's owner and Project members may work with it, but account membership is required. Administrators do not automatically gain execution access to someone else's computer.
Reconnect and retry safely
- Restore the computer's network connection and make sure it is powered on.
- Start or restart its Elowen client connection; on a paired CLI computer, use
elowen connect. - Wait until the status shows it online.
- Retry only after establishing whether the earlier command completed. For file changes or other side effects, inspect the actual result first.
A successful reconnection does not resume a command whose result was lost. Avoid repeating non-idempotent actions such as uploads, deletions or publishing until you know what happened.
Common problems
If the client does not reconnect after a restart, check that its background connection is configured for the operating system; the CLI guide describes how it starts. For interactive terminals on a computer Project, reconnecting ends the old terminal, so open a new one. If the machine remains offline, use another Project only after explicitly selecting it and confirming that it is the intended execution target.
Related guides
See CLI for connection startup and Projects, Environments & GitHub for computer Project access.