Using the app

Updates & moving servers

Install signed updates, return to a previous version, and move your setup to a new server.

Updating

Open Settings → Updates. ⟳ Check for updates looks for a signed update without installing it; Update now installs it.

The app saves its state and stops cleanly before replacing any code. Resting exchange orders keep working; app-held stops and timed DCAs pause during the restart.
Your settings, history and trading data are kept. An update never closes positions.
Never re-run the installer to upgrade.

If an update fails, a banner shows the reason and Try again. Your current version keeps running and nothing was changed. Try once more; if it repeats, send a bug report.

Warning. If you see "Release recovery needs attention. Do not start another update.", stop pressing Update and send a bug report (Contact Support). It includes release diagnostics automatically.

A locked or refused exchange account does not block updates.

Returning to a previous version

The Updates card shows Approved previous version: vX with a Return to vX button, or "No compatible previous version is available." Reverting restarts the app and keeps your data. If a stop-loss fill is still being booked, it asks you to wait.

Moving to a new server

On the old server: Settings → Move existing setup → Export setup.
On the new server: connect the same exchange accounts, then Import setup and choose each destination account explicitly.
Imported bots arrive paused. Re-enter Discord and TradingView webhook secrets.
Stop the old server before the new one trades. Two running servers on one account conflict.

Open positions, trading history and per-deal state are not transferred. Close or hand over positions first (the Manual Bot can take over open positions on the new server).

Restarting or a blank page

A browser showing 502 Bad Gateway right after an update or restart usually means the app is still starting. Wait a minute and reload. If it persists, contact Support.