Deployment
Console agents need somewhere to run. Each Syntic project that uses agents gets its own runtime node: an isolated environment that hosts the project’s AI agents and AI staff, holds their sessions and keeps their channels connected. Projects do not share nodes, so one project’s load or failure does not touch another’s.
You manage the node from Agent Deployment in the Console.
Deploying, restarting and powering a node need the administrator or owner role. Other members can see its status.
Deploy a runtime
Select the project
Choose the organization and project in the Console. If no project is selected, Agent Deployment asks you to pick one first.
Open Agent Deployment
If the project has no runtime yet, the page offers to provision one.
Choose a region
Pick the region closest to the people and systems the agents will talk to:
| Region |
|---|
| Ashburn, US East |
| Chicago, US Central |
| San Jose, US West |
| London, UK |
| Frankfurt, Germany |
| Amsterdam, Netherlands |
| Singapore |
| Sydney, Australia |
Decide on Always-on
The Always-on switch is on by default.
- On: the node keeps running all the time. Leave it on for any agent that listens on a channel, so messages are answered at once.
- Off: the node may sleep when idle and wake when it is needed. This suits agents that only run from the Console or a workflow.
Deploy
Start the deployment. The status reads Provisioning and the page checks again every 10 seconds until the node is Running.
What the page shows
Once a node exists, Agent Deployment shows:
| Field | Meaning |
|---|---|
| Status | Provisioning, Running or Suspended. |
| Endpoint | The node’s address. |
| Version | The runtime version the node is on. |
| Uptime | How long the node has been running. |
| Channels connected | How many channels are live. |
| Connected channels | Each channel with its own status. |
Power and restart
| Action | What happens | Use it when |
|---|---|---|
| Restart | The node restarts. Active conversations may pause briefly. | Agents are stuck or a change has not taken effect. |
| Suspend | The node sleeps and keeps its memory, so it resumes quickly. | You want to pause agents for a while. |
| Stop (kill-switch) | The node halts at once. Channels disconnect and nothing is processed until it is started again. The status shows Suspended. | Emergency stop: an agent is misbehaving and must stop now. |
| Start | Wakes a suspended or stopped node. | Resuming work. |
Start, Suspend and Stop (kill-switch) sit on the Node Power card. Restart is always available; Node Power appears only on node types that support it.
Stop is the project’s kill switch. Use it first and investigate afterwards.
Agent status and the runtime
An agent can only take work when its project’s node is running. If an agent is marked Running but the project has no node, its card shows Not deployed instead, and the roster’s Not deployed filter lists every such agent. Deploying a runtime fixes all of them at once.
Troubleshooting
| What you see | What to try |
|---|---|
| ”This project has no runtime yet” | Deploy one as described above. |
| Status stays on Provisioning much longer than usual | Refresh the page, then contact support with the project name. |
| Agents stop answering on a channel | Check the channel’s status here, then select Restart. |
| Node shows Suspended unexpectedly | An administrator may have stopped it, or an on-demand node went to sleep. Select Start. |