Launch and control
What a launch needs, how to choose a machine, which settings apply, and how failures are surfaced.
On this page
Before you start
- No machine online means Start is unavailable until an agent connects.
- An account with no credentials can be tracked but not launched.
- Each machine has a maximum number of clients it will run at once.
Choose a machine
Where to find itDashboard / Accounts / Actions
With one machine online, Kovex uses it automatically. With several, you choose which machine should run the account, which is how you keep pools separated by hardware or location.
Launch settings
Settings resolve in one order: the profile first, then its category, then the product default.
- Client
- Which client the machine should start. The menu lists what is available there.
- World
- A fixed world, a random free world, a random member world, or automatic.
- Script and arguments
- The task to start with the client and any arguments it expects.
- Advanced options
- Memory, interface scale, and similar per machine tuning.
Start and stop
- StartUse the row action for one account, or the toolbar for a selection. You can override the client for this launch only.
- Watch the statusLaunching means the request was accepted. Running means the client reported telemetry.
- StopStop closes the client cleanly and frees the slot on that machine.
When a launch fails
Start does nothing and the button explains that no agent is connected.
- Likely cause
- No machine is online.
- Check
- Look at the connected machines list.
- Resolution
- Start the agent on your machine, wait for it to show as connected, then start again.
The launch is refused because the machine is at capacity.
- Likely cause
- That machine already runs its maximum number of clients.
- Check
- Count the running accounts on that machine in Live.
- Resolution
- Stop a client, or pick another machine that has room.
The status changes to Error shortly after Start.
- Likely cause
- The client could not start, or the account session was rejected.
- Check
- Read the message on the row, then confirm the client path and the account credentials.
- Resolution
- If the client could not start, correct its setup. If the session was rejected, test the account's proxy, then re-authenticate the account. Then start again. See Troubleshooting.
Related guides
Still blocked?
Send us the guide you were following and what you saw instead. You get a private case link to track the answer.