To avoid a single point of failure, configure a secondary remote agent as a backup.
If the primary agent becomes unavailable, the secondary agent automatically takes over remote execution of actions, jobs, and connectors after a 30-second downtime.
If the primary agent fails while executing a task, that task fails and must be manually re-run.
All other pending tasks are routed to the secondary agent.
Once the primary agent is restored, all jobs, actions, and connectors seamlessly switch back to it.
To set up high availability for remote agents, do the following:
Go to SOAR settings > Advanced > Remote Agents.
Click View more on the agent you want to set as primary and assign a
secondary agent. The side drawer opens
with all the information on the agent.
Click Add secondary agent. You can create one secondary agent for
each primary agent. You cannot use the same secondary agent for two different
primary agents.
If your primary agent is not updated to the latest version, a message
prompts you to click Update.
If your connectors are on an older version, you're prompted to redeploy them to
support high availability.
For more information, see Redeploy connectors.
Follow the process to set up an agent. You can choose to set up the agent using
manual installation or a docker. Make sure the secondary agent has the same network or internet access
as the primary agent. The status of the secondary agent is shown as live in the High Availability
column in the Remote Agents page.
Notifications
Agent notifications—such as alerts for new agent versions and agent
downtime—are enabled by default. Notifications for agent downtime are triggered
when a remote agent has been down for more than 90 seconds. You can opt out of
these notifications at any time from your user preferences.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eHigh availability for remote agents in Google SecOps SOAR can be achieved by configuring a secondary agent as a backup to the primary agent.\u003c/p\u003e\n"],["\u003cp\u003eThe secondary agent automatically takes over if the primary agent becomes unavailable, after a 30-second downtime, ensuring continuous remote execution of actions, jobs, and connectors.\u003c/p\u003e\n"],["\u003cp\u003eOnly one secondary agent can be assigned to each primary agent, and a secondary agent cannot be shared between multiple primary agents.\u003c/p\u003e\n"],["\u003cp\u003eTo enable this feature, you can navigate to the Remote Agents section in SOAR settings and add a secondary agent to a selected primary agent.\u003c/p\u003e\n"],["\u003cp\u003eNotifications are triggered after a remote agent has been down for 90 seconds, which is a longer time frame than when the secondary takes over.\u003c/p\u003e\n"]]],[],null,["# Deploy high availability in remote agents\n=========================================\n\nSupported in: \nGoogle secops [SOAR](/chronicle/docs/secops/google-secops-soar-toc)\n| **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).\n\nTo avoid a single point of failure, configure a secondary remote agent as a backup.\nIf the primary agent becomes unavailable, the secondary agent automatically takes over remote execution of actions, jobs, and connectors after a 30-second downtime.\nIf the primary agent fails while executing a task, that task fails and must be manually re-run.\nAll other pending tasks are routed to the secondary agent.\nOnce the primary agent is restored, all jobs, actions, and connectors seamlessly switch back to it.\n\nTo set up high availability for remote agents, do the following:\n\n1. Go to **SOAR settings \\\u003e Advanced \\\u003e Remote Agents.**\n2. Click **View more** on the agent you want to set as primary and assign a secondary agent. The side drawer opens with all the information on the agent.\n3. Click **Add secondary agent**. You can create one secondary agent for each primary agent. You cannot use the same secondary agent for two different primary agents.\n - If your primary agent is not updated to the latest version, a message prompts you to click **Update**.\n - If your connectors are on an older version, you're prompted to redeploy them to support high availability. For more information, see [Redeploy connectors.](/chronicle/docs/soar/working-with-remote-agents/redeploy-connectors-remote-agents)\n4. Follow the process to set up an agent. You can choose to set up the agent using manual installation or a docker. Make sure the secondary agent has the same network or internet access as the primary agent. The status of the secondary agent is shown as live in the **High Availability** column in the **Remote Agents** page.\n\n\u003cbr /\u003e\n\n| **Note:** Once you set up high availability, you can only work with the primary agent across the platform. If the primary agent is down, the secondary agent becomes active, ensuring a seamless configuration deployment..\n\nNotifications\n-------------\n\nAgent notifications---such as alerts for new agent versions and agent\ndowntime---are enabled by default. Notifications for agent downtime are triggered\nwhen a remote agent has been down for more than 90 seconds. You can opt out of\nthese notifications at any time from your user preferences.\n\nFor more information, see [Agent notifications](/chronicle/docs/soar/working-with-remote-agents/what-is-a-remote-agent#agent-notifications).\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
