States and lifecycle

An execution is a specific run of a process on an agent. From creation to completion, it goes through a series of well-defined states. Knowing them allows you to know, at a glance, what is happening and why.

The life cycle

stateDiagram-v2
  [*] --> queued
  queued --> running
  queued --> cancelled: cancelada antes de empezar
  running --> completed: terminó bien
  running --> failed: terminó con error
  running --> cancelled: cancelada en ejecución
  completed --> [*]
  failed --> [*]
  cancelled --> [*]

Estado	Description	How to get there
queued	In queue, waiting for the selected agent to receive it	When creating the execution (manual or by trigger)
running	The agent is running the process	The agent receives the order and begins
completed	Completed successfully (exit code 0)	The playbook finished without errors
failed	Ended with error	Playbook error, exit code ≠ 0, or agent disconnection
cancelled	Cancelada manualmente antes de terminar	A user canceled it from the portal

Cada estado en detalle

queued

The execution exists but the selected agent has not yet received it. It usually lasts seconds. If you stay here, that agent is usually offline or busy. See Agent Monitoring.

running

The agent downloaded the package and is running the playbook. Here you see the real-time logs. The status of the agent running it appears as busy.

completed

The playbook reached the end without throwing an error and returned exit code 0. It is the expected result of a healthy run.

failed

Something prevented the execution from being completed. Typical causes:

• An activity threw an unhandled error (a selector that does not appear, a file that does not exist, a credential that does not resolve).
• The playbook ended with an exit code other than 0.
• The agent disconnected during execution and did not reconnect within the grace period.

Always check the logs to see the exact cause.

cancelled

A user stopped the run manually from the portal before it finished. Useful for killing a process that was stuck or launched by mistake.

Reintentos

Zoan Cloud does not retry alone

A failed execution is not automatically retried. If you need to run it again, launch a new manual run or set a trigger.

For retries within the automation (for example, retrying an unstable web action), use the Retry activity in the playbook layout. See Debugging › Retry.

Agent disconnection

If the agent running a run loses connection to Zoan Cloud and does not reconnect within a grace period (~3 minutes), the run is automatically marked as failed. This prevents a run from being “hung” indefinitely if the machine goes down or the network goes down.

It is a different time than it takes for the agent to display offline (~2 minutes without heartbeat). One monitors the agent’s health; the other, the destination of a specific execution.

Execution time

The platform does not impose a duration limit: a process can take seconds or hours depending on what it does. The run detail shows its total duration once completed.

Next steps

• Execution Logs — diagnose what happened.
• Run manually — retry after failure.
• Agent Monitoring — why something stays on queued.