The connector redeployment process is connected to the
remote agent high availability feature.
When you redeploy connectors, the connector's scheduler moves from the remote agent to the Google SecOps server. The redeployment process can be performed
manually for each remote agent. During this process, validation checks are conducted on each connector. If it detects any issues,
all changes are automatically reverted and the connector is restored to its previous working state.
The redeploy process may take some time. You can track the completion of the process on the remote agent page.
If you get an error message, we recommend
that you repeat the redeployment process.
If that fails, contact Google Support.
[[["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-09-04 UTC."],[[["\u003cp\u003eConnectors can be redeployed manually for each remote agent within Google SecOps SOAR.\u003c/p\u003e\n"],["\u003cp\u003eRedeploying connectors moves their scheduler from the remote agent to the Google SecOps server.\u003c/p\u003e\n"],["\u003cp\u003eValidation checks are performed during redeployment, and any issues will result in an automatic revert to the previous state.\u003c/p\u003e\n"],["\u003cp\u003eThe connector redeployment is linked to the remote agent high availability feature, and you can track the progress on the remote agent page.\u003c/p\u003e\n"],["\u003cp\u003eRedeployment is a Pre-GA feature with limited support, and if errors persist after reattempting the process, you should contact Google Support.\u003c/p\u003e\n"]]],[],null,["# Redeploy connectors\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\nThe connector redeployment process is connected to the\n[remote agent high availability feature](/chronicle/docs/soar/working-with-remote-agents/deploy-high-availability-for-remote-agents).\nWhen you redeploy connectors, the connector's scheduler moves from the remote agent to the Google SecOps server. The redeployment process can be performed\nmanually for each remote agent. During this process, validation checks are conducted on each connector. If it detects any issues,\nall changes are automatically reverted and the connector is restored to its previous working state.\n\nThe redeploy process may take some time. You can track the completion of the process on the remote agent page. \n\nIf you get an error message, we recommend\nthat you repeat the redeployment process.\nIf that fails, contact [Google Support](https://console.cloud.google.com/support)."]]
