Actions27
- Alert Actions
- Diagnostic Actions
- Firewall Actions
- Firewall Group Actions
- Firmware Actions
- Health Actions
- Licensing Actions
- Organization Actions
- Partner Actions
Firmware → Upgrade
AI-generatedSummary
Trigger an immediate or scheduled firmware upgrade for one Sophos Central firewall. The operation sends the requested version to Sophos Central; it can optionally poll until the firewall reports that version.
Inputs
- Tenant — Select a tenant from the list or provide its ID. Partner credentials require a tenant; with Organization credentials, the tenant can come from the credential.
- Firewall (required) — Select a firewall or provide its ID.
- Target Version (required) — Choose an available version from the list or enter a version string.
- Schedule Type — Choose Immediate (default) or Scheduled.
- Scheduled Time (required) — For a scheduled upgrade, provide the start time in ISO 8601 format.
- Create Backup Before Upgrade — Defaults to false. Enabling this causes the operation to fail: Sophos Central Firewall API v1 does not expose backup endpoints.
- Wait for Completion — Defaults to false. When enabled, polls the firewall until it reports the target version. Polling interval defaults to 30 seconds (10–300); timeout defaults to 1800 seconds (60–7200).
- Additional Fields — Auto Revert on Failure defaults to true, but is only returned as requestedOptions and is not sent in the API request. Backup Description is unused.
Output shape
One item containing the Sophos upgrade response, plus requestedOptions.autoRevert; when waiting for completion, one item containing upgradeResponse, finalCheck, and requestedOptions.autoRevert.
The upgrade is submitted through Sophos Central's firmware-upgrade endpoint. For scheduled upgrades, the supplied time is parsed and sent as an ISO 8601 timestamp. With Wait for Completion enabled, the node checks periodically until the reported firmware version matches the target, then returns the final check; it raises a timeout error if the configured wait limit is exceeded. Errors follow the node's continue-on-fail behavior.