Monitoring and states

From the portal you can see, in real time, the status of all the agents in an environment. Knowing if an agent is available is the first thing you check when an automation is not running: without a online agent, executions are left waiting.

Agent States

Estado	Color	Significado	What to do
online	🟢 Verde	Connected and available to receive executions	Nothing — it’s ready
busy	🟠 Naranja	Running a process right now	Wait for it to finish, or use another agent
offline	⚪ Gris	No active connection to Zoan Cloud	Check out troubleshooting

The status changes on its own, without you having to refresh the page.

The heartbeat

The agent sends Zoan Cloud a periodic heartbeat while connected - its way of saying “I’m still here.” If Zoan Cloud stops receiving heartbeats for more than 2 minutes, it considers the connection lost and marks the agent as offline automatically.

Note

This is why it can take up to ~2 minutes for an agent to switch to offline after, for example, your machine shuts down or your network goes down. It’s not a bug: it’s the grace period before declaring it offline.

Metrics Dashboard

Above the list of agents, the panel summarizes the status of the environment:

Metric	What counts
Total	Registered agents in the environment
Online	Conectados y disponibles
Ocupados	Running a process right now
Offline	Offline
Disponibles	Online and free, ready to receive an execution

If Available is 0, a new execution will be queued (queued) until an agent is released or reconnected.

Troubleshooting

Agent appears offline right after connecting

• Verify that the Machine Key configured in the Agent is correct (without spaces at the beginning or end). See Settings.
• Make sure the machine has outgoing network access to the Zoan Cloud server on port 443 (HTTPS/WSS).
• If there is a corporate proxy, it should allow WebSocket (wss://) connections, not just regular HTTP.

The agent is online but does not receive executions

• Confirm that the process you are trying to run is assigned to that agent/environment. See Execute manually.
• Check that the agent is not busy with a hanging execution. If you suspect it is stuck, cancel it from the Runs tab.
• Verifies that the process package is in a version compatible with the packages installed on that agent.

The agent alternates between online and offline

• This usually indicates an unstable network connection or a proxy that is cutting off inactive WebSockets. Check that machine’s network stability and proxy settings.

Next steps

• Windows Installation — includes more installation diagnostics.
• States and life cycle of an execution.