Skip to content

MAX_RETRY_ATTEMPTS_FAILED

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
MAX_RETRY_ATTEMPTS_FAILED
Likely outcomes (0 missions) — click to expand

Based on 0 missions where this alarm fired in the last 90 days as of 2026-10-13

Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.

On 2026.15 and older, MAX_RETRY_ATTEMPTS_FAILED sets when the Aircraft fails to start charging 5 times in a row. The zip will remain unable to charge until the underlying charging alarm is addressed and the distro is reset.

On 2026.15.1 and newer, repeated charge-start failures first set SLOW_CHARGE_RECOVERY_ACTIVE. The zip then retries charging over a 24-hour recovery window. MAX_RETRY_ATTEMPTS_FAILED sets only if that recovery window expires without a successful charge-start attempt. Charger-reported DeltaQ faults should keep retrying instead of putting the Dock into FAULTED_UNRECOVERABLE/DEGRADED, but other faults can still make the Dock DEGRADED.

1 action >=2026.15.1
On 2026.15.1 and newer, MAX_RETRY_ATTEMPTS_FAILED means the 24-hour slow charge recovery window has expired without a successful charge-start attempt. Treat this as a persistent charging failure. Open the Aircraft/Droid Alarm Report and note the Zip ID, Dock ID, mission identifier, and dock_asset_id; use the earlier SLOW_CHARGE_RECOVERY_ACTIVE alarm report if it has better Dock context.

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.