Run manually

A manual execution is launching a process by hand, on the fly, from the portal. It is the most direct way to run an automation and the one you use to test that everything was correctly configured before programming it with a trigger.

Requirements

• A process created and in state active.
• At least one connected machine in the environment (if the process is in a folder, assigned to that folder). See Machine monitoring and Folders and access.
• For Windows desktop processes, a robot session (the Windows account the bot will run under). Sin pantalla (headless) processes don’t need one and can also run on Zoan Cloud.

From the Executions tab

1. Pick the environment at the top right and open Centro › Robots › Ejecuciones (Center › Robots › Executions).
2. Click Iniciar ejecución (Start execution).
3. Select the Proceso (Process) you want to run.
4. Pick the Máquina (Machine) and the Sesión de robot (Robot session). With Agregar máquina (Add machine) you launch the same run on several machines at once: each row is one execution.
5. If the process takes data, fill in the Argumentos del proceso (Process arguments), as a form or JSON.
6. Optionally set a Duración máxima (see Maximum duration).
7. Click Iniciar (Start). If something would stop it from running (a disconnected machine, or one without access to the folder), the portal tells you first.

You choose the machine and the session

The execution is not automatically dispatched: you explicitly choose the machine and the robot session. That way you always know where each robot runs. If you pick a busy or disconnected machine, the execution waits in queue until it is available.

From the Processes tab

You can also launch the execution directly from the process list, with each process’s ▶ Iniciar ejecución button. It is an equivalent shortcut that avoids selecting the process again.

What happens next

The execution goes through its lifecycle:

1. It enters state queued (queued), waiting for the machine you chose to receive it.
2. When that machine receives it, it goes to running and starts working.
3. When finished, it is completed (success) or failed (error).

From the same screen you see progress and logs in real time, without refreshing. See Execution Logs.

If it gets stuck in queued

It means the machine you chose has not received it yet. The usual causes: it is Desconectada (Disconnected) or Ocupada (Busy), or the process is not compatible with it. The execution detail shows why it is waiting; check Centro › Máquinas and, if needed, launch it again on another machine.

When to use manual execution

Use it to…	For recurring, use…
Test a newly created process	—
One-off reports or tasks on demand	—
Reprocess something that failed	—
One-time migrations or maintenance	—
A task that runs every day/week	Trigger programado

Next steps

• States and life cycle — what each state means.
• Execution logs — read what the bot did.
• Scheduled Triggers — automate when.