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.
Requisitos
Section titled “Requisitos”- A process created and in state
active. - At least one agent
onlinein the environment. See Agent Monitoring. - A robot session configured in the environment (the Windows account the bot will run under).
From the Executions tab
Section titled “From the Executions tab”- Enter the environment and open the Executions tab.
- Click New Run.
- Select the process you want to run.
- Select the agent that will execute it.
- Select the robot session it will run with. See Robot sessions.
- Confirma.
From the Processes tab
Section titled “From the Processes tab”You can also launch the execution directly from the process list, with the process execution button. It is an equivalent shortcut that avoids selecting the process again.
What happens next
Section titled “What happens next”The execution goes through its lifecycle:
- It enters state
queued(queued), waiting for the agent you chose to receive it. - When that agent receives it, he goes to
runningand starts working. - When finished, it is
completed(success) orfailed(error).
From the same screen you see progress and logs in real time, without refreshing. See Execution Logs.
When to use manual execution
Section titled “When to use manual execution”| Use it to… | For recurring, use… |
|---|---|
| Test a newly created process | — |
| Reportes o tareas puntuales bajo demanda | — |
| Reprocess something that failed | — |
| One-time migrations or maintenance | — |
| A task that runs every day/week | Trigger programado |
Next steps
Section titled “Next steps”- States and life cycle — what each state means.
- Execution logs — read what the bot did.
- Scheduled Triggers — automate when.