Update the server

This page updates the API, Worker, Studio and app store of your server to a newer release. Services can be briefly unavailable. Apps keep running on their Runners.

Prerequisites

You are a system administrator, and the CLI is signed in to the server: automaton login --server https://api.example.com.
A server installed with the current installer. Older servers get the update trigger the first time update.sh runs over SSH (see the fallback below).
Servers still on MySQL cannot take this update; move them first with the migration guide.

Steps

Update and wait.
bash
```
automaton server update --wait
```
Pin a release with --version server-vX.Y.Z. The API restarts during the update; --wait follows it, then checks /health and the installed version, and exits nonzero on failure with the log tail and the recovery backup. --timeout SECONDS defaults to 1800.
In Studio instead: Admin → Installation → Update (the Update to the latest release button).
Check the last run any time.
bash
```
automaton server update-status
```

A release older than the installed one is refused unless you pass --allow-downgrade (Studio does not offer it).

Fallback over SSH

bash

sudo bash /opt/automaton-server/update.sh            # latest
sudo bash /opt/automaton-server/update.sh --version server-vX.Y.Z

Verify it worked

bash

curl -fsS https://api.example.com/health
automaton installation-status

Expected: ok, and Version: shows the new release.

Common errors

Not picked up within two minutes. On the server run systemctl status automaton-update.path.
HTTP 409. Another update is running; wait for it.
Update failed. The previous release and a recovery backup are kept; the log names the backup. Do not rerun blindly. Restore with Back up and restore if a migration already ran.

How the trigger works (the API never runs as root), adopted installs and recovery: operator reference.

Update the server ​

Prerequisites ​

Steps ​

Fallback over SSH ​