Celigo · On-premise agent groups
No agent in an agent group is available
Short answer
A Celigo flow run or connection test fails this way when every agent in the agent group is offline or unresponsive. Go to Resources, then On-premise agents, and check the status of each agent in the group.
VerifiedLast verified
01Error text
No agent in an agent group is available02Likely causes
- Every agent in the group is offline, has gone 60 seconds without a heartbeat, or failed with a connection error.
03How to fix it
- Go to Resources, then On-premise agents, and check the status of each agent in the group.
- Bring at least one agent back online.
- Retry the failed flow runs.
iNotes
A group can have up to three agents. Celigo recommends installing each agent on a separate machine.
04Official documentation
→Related errors
- On-premise agent: Offline (red) statusAn Offline (red) status for a Celigo on-premise agent means the agent is not running, its token does not match, or a firewall or proxy is blocking it. Check that the agent is running, that its token matches the token in integrator.io, and that no firewall or proxy blocks it.
- On-premise agent: No logs or empty log filesMissing or empty log files for a Celigo on-premise agent mean the agent is running with incorrect permissions, or the log path is misconfigured or inaccessible. Determine whether the log files exist on the machine.
- On-premise agent: Failed to uninstall old application filesThis Celigo on-premise agent error means the Windows system PATH environment variable is corrupted or inconsistent after the agent auto-update. Restart the system.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Celigo work:Open Celigo jobsCeligo rates and salaries