Skip to article
XTester Help
XTester Launcher

Troubleshooting

Check why a robot will not start, receives no data or loses its connection.

Reviewed: Applies to: 1.0.0-preview.1

The robot does not start

• Start is disabled: the launch profile has an error, and the button's tooltip names it. Open the Profile.

• Market busy: another robot already works on this pair. Stop it or choose another pair.

• API keys required: add keys in Connections or choose an account with keys in the profile.

• The robot is not ready to start: the pre-start check failed; the reasons are in the journal.

• The robot is already running or preparing to start: stop it first.

LIVE is blocked

• Keys unavailable or LIVE is unavailable: the secure key storage on the computer does not respond; only Paper is available.

Application screenshotXTester 1.0.0-preview.1
In this example Launcher blocked startup before exchange operations. Open Connections takes you to the settings.Interface screenshot · XTester 1.0.0-preview.1
  1. Blocking reason

• Key storage unavailable: there is no need to enter the keys again. Restart the launcher; if that does not help, check the system's secure key storage.

• Verification failed when checking keys: check the keys, the network (Mainnet or Sandbox) and the key's permissions on the exchange.

• LIVE · exchange not ready: check the keys, the network, the pair, the API key permissions, open orders and the position.

• Other robots or a named server could not be checked: open the correct XTester Studio window and check its server connection. Update the Agent through the ordinary command when needed. An empty or old list does not prove absence. The check does not install anything or accept a new server host key.

• A server Live resume needs its Studio window to check other robots: resume from that XTester Studio profile. A web-panel read permission cannot bypass the check.

No data or an empty chart

Look at the status bar: Data stopped means quotes stopped coming, Data: failed means the candle history did not load. Check the internet connection. While the robot loads its history, the chart shows Loading the history….

The launcher lost its service process

If the launcher says it lost the connection to its service process, the robot of this window is no longer managed: it stops trading, and its orders and position stay on the exchange as they are. Close the window, open the launcher again and check the account on the exchange.

Application screenshotXTester 1.0.0-preview.1
After the test process was terminated, Launcher recorded exit code 137 and began the first of three restart attempts. Select Why? to open the Journal.Interface screenshot · XTester 1.0.0-preview.1

When to check the exchange by hand

• A notification The exchange did not confirm the cancellation or The exchange did not confirm closing the position.

• The check the exchange warning in the status bar after a stop.

• After a LIVE robot ended abnormally.

In each case open the exchange and check the robot's orders and position. The details are in the journal.