MAX_RETRY_ATTEMPTS_FAILED
This alarm is covered by this guide. Applicable alarms (1)
Likely outcomes — 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.
Background
Section titled “Background”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.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
max-retry-after-slow-recovery-expired["<small><b>Step 1</b></small><br/>Action: On 2026.15.1 and newer, MAX_RETRY_AT..."]
load-charging-alarm-plot-new["<small><b>Step 2</b></small><br/>Telemetry: Load the charging alarm plot for the ..."]
check-dock-degraded-new{"<small><b>Step 3</b></small><br/>Question: At the charge-start failure time you ..."}
power-cycle-dock-breaker-for-dock-charging-state-new["<small><b>Step 4</b></small><br/>Action: Follow Power Cycle / Reset Tripped D..."]
did-breaker-restore-dock-status-new{"<small><b>Step 5</b></small><br/>Question: Did the Dock status recover after the..."}
replace-charger-after-dock-breaker-new["<small><b>Step 6</b></small><br/>Action: Create a work order to replace the ch..."]
select-charging-alarm-new{"<small><b>Step 7</b></small><br/>Question: With those Dock conditions ruled out,..."}
power-cycle-aircraft-after-dock-charger-clears["<small><b>Step 8</b></small><br/>Action: With the Dock charging condition clea..."]
load-charging-alarm-plot-legacy["<small><b>Step 9</b></small><br/>Telemetry: Load the charging alarm plot for the ..."]
select-charging-alarm-legacy{"<small><b>Step 10</b></small><br/>Question: Which related charging alarm is set i..."}
charger-fault-status-check-dock-degraded{"<small><b>Step 11</b></small><br/>Question: At the time UNEXPECTED_CHARGER_FAULT..."}
charger-fault-status-escalate-dock-embedded{{"<small><b>Step 12</b></small><br/>Escalation: Escalate to P2 Dock Embedded On Call...."}}
unexpected-charge-voltage-escalate-firmware-power{{"<small><b>Step 13</b></small><br/>Escalation: Escalate to P2 Firmware Power On Call..."}}
relay-open-check-dock-degraded{"<small><b>Step 14</b></small><br/>Question: At the time DOCK_RELAY_FAILED_TO_OPE..."}
relay-open-escalate-dock-hardware{{"<small><b>Step 15</b></small><br/>Escalation: Escalate to P2 Dock Hardware On Call...."}}
relay-close-check-dock-degraded{"<small><b>Step 16</b></small><br/>Question: At the time DOCK_RELAY_FAILED_TO_CLO..."}
relay-close-restart-charger-service["<small><b>Step 17</b></small><br/>Action: Restart the Dock charger service/p..."]
relay-close-escalate-dock-hardware{{"<small><b>Step 18</b></small><br/>Escalation: Escalate to P2 Dock Hardware On Call...."}}
failed-to-ramp-check-dock-degraded{"<small><b>Step 19</b></small><br/>Question: At the time FAILED_TO_RAMP_CURRENT ..."}
failed-to-ramp-redock-aircraft["<small><b>Step 20</b></small><br/>Action: Redock the same Aircraft on the same ..."]
failed-to-ramp-did-redock-resolve{"<small><b>Step 21</b></small><br/>Question: Did redocking start charging normally..."}
failed-to-ramp-inspect-fin-pins-distro["<small><b>Step 22</b></small><br/>Action: Complete the UMM detailed battery in..."]
failed-to-ramp-were-issues-found{"<small><b>Step 23</b></small><br/>Question: Did the battery/distro or docking-fin..."}
failed-to-ramp-escalate-aircraft-hardware{{"<small><b>Step 24</b></small><br/>Escalation: Escalate to P2 Aircraft Hardware On C..."}}
failed-to-ramp-create-dock-charger-work-order["<small><b>Step 25</b></small><br/>Action: Create a work order to replace the ch..."]
charge-timeout-check-dock-degraded{"<small><b>Step 26</b></small><br/>Question: At the time CHARGE_CURRENT_TIMEOUT ..."}
charge-timeout-escalate-dock-hardware{{"<small><b>Step 27</b></small><br/>Escalation: Escalate to P2 Dock Hardware On Call...."}}
check-dock-health{"<small><b>Step 28</b></small><br/>Question: Using the Dock ID from the alarm repo..."}
troubleshoot-dock-charging-issue["<small><b>Step 29</b></small><br/>Action: Treat the Dock condition as the prima..."]
did-charging-start-after-reset{"<small><b>Step 30</b></small><br/>Question: Did charging start normally after the..."}
return-to-service-after-charging-starts["<small><b>Step 31</b></small><br/>Action: Return the Aircraft to service."]
escalate-to-firmware-power-after-reset{{"<small><b>Step 32</b></small><br/>Escalation: Escalate to P2 Firmware Power On Call..."}}
escalate-to-firmware-power{{"<small><b>Step 33</b></small><br/>Escalation: Escalate to P2 Firmware Power On Call..."}}
max-retry-after-slow-recovery-expired --> load-charging-alarm-plot-new
load-charging-alarm-plot-new --> check-dock-degraded-new
check-dock-degraded-new -->|Dock was DEGRADED| power-cycle-dock-breaker-for-dock-charging-state-new
check-dock-degraded-new -->|UNEXPECTED_CHARGER_FAULT_S...| power-cycle-dock-breaker-for-dock-charging-state-new
check-dock-degraded-new -->|UNEXPECTED_CHARGER_FAULT_S...| charger-fault-status-escalate-dock-embedded
check-dock-degraded-new -->|No Dock condition above is ...| select-charging-alarm-new
power-cycle-dock-breaker-for-dock-charging-state-new --> did-breaker-restore-dock-status-new
did-breaker-restore-dock-status-new -->|Yes| power-cycle-aircraft-after-dock-charger-clears
did-breaker-restore-dock-status-new -->|No| replace-charger-after-dock-breaker-new
select-charging-alarm-new -->|UNEXPECTED_CHARGE_VOLTAGE| unexpected-charge-voltage-escalate-firmware-power
select-charging-alarm-new -->|DOCK_RELAY_FAILED_TO_OPEN| relay-open-escalate-dock-hardware
select-charging-alarm-new -->|DOCK_RELAY_FAILED_TO_CLOSE| relay-close-restart-charger-service
select-charging-alarm-new -->|FAILED_TO_RAMP_CURRENT| failed-to-ramp-redock-aircraft
select-charging-alarm-new -->|CHARGE_CURRENT_TIMEOUT| charge-timeout-escalate-dock-hardware
select-charging-alarm-new -->|No related charging alarm i...| escalate-to-firmware-power
power-cycle-aircraft-after-dock-charger-clears --> did-charging-start-after-reset
load-charging-alarm-plot-legacy --> select-charging-alarm-legacy
select-charging-alarm-legacy -->|UNEXPECTED_CHARGER_FAULT_S...| charger-fault-status-check-dock-degraded
select-charging-alarm-legacy -->|UNEXPECTED_CHARGE_VOLTAGE| unexpected-charge-voltage-escalate-firmware-power
select-charging-alarm-legacy -->|DOCK_RELAY_FAILED_TO_OPEN| relay-open-check-dock-degraded
select-charging-alarm-legacy -->|DOCK_RELAY_FAILED_TO_CLOSE| relay-close-check-dock-degraded
select-charging-alarm-legacy -->|FAILED_TO_RAMP_CURRENT| failed-to-ramp-check-dock-degraded
select-charging-alarm-legacy -->|CHARGE_CURRENT_TIMEOUT| charge-timeout-check-dock-degraded
select-charging-alarm-legacy -->|No related charging alarm i...| check-dock-health
charger-fault-status-check-dock-degraded -->|Yes| troubleshoot-dock-charging-issue
charger-fault-status-check-dock-degraded -->|No| charger-fault-status-escalate-dock-embedded
relay-open-check-dock-degraded -->|Yes| troubleshoot-dock-charging-issue
relay-open-check-dock-degraded -->|No| relay-open-escalate-dock-hardware
relay-close-check-dock-degraded -->|Yes| troubleshoot-dock-charging-issue
relay-close-check-dock-degraded -->|No| relay-close-restart-charger-service
relay-close-restart-charger-service --> relay-close-escalate-dock-hardware
failed-to-ramp-check-dock-degraded -->|Yes| troubleshoot-dock-charging-issue
failed-to-ramp-check-dock-degraded -->|No| failed-to-ramp-redock-aircraft
failed-to-ramp-redock-aircraft --> failed-to-ramp-did-redock-resolve
failed-to-ramp-did-redock-resolve -->|Yes| return-to-service-after-charging-starts
failed-to-ramp-did-redock-resolve -->|No| failed-to-ramp-inspect-fin-pins-distro
failed-to-ramp-inspect-fin-pins-distro --> failed-to-ramp-were-issues-found
failed-to-ramp-were-issues-found -->|Yes| failed-to-ramp-escalate-aircraft-hardware
failed-to-ramp-were-issues-found -->|No| failed-to-ramp-create-dock-charger-work-order
charge-timeout-check-dock-degraded -->|Yes| troubleshoot-dock-charging-issue
charge-timeout-check-dock-degraded -->|No| charge-timeout-escalate-dock-hardware
check-dock-health -->|Yes| troubleshoot-dock-charging-issue
check-dock-health -->|No| escalate-to-firmware-power
troubleshoot-dock-charging-issue --> did-charging-start-after-reset
did-charging-start-after-reset -->|Yes| return-to-service-after-charging-starts
did-charging-start-after-reset -->|No| escalate-to-firmware-power-after-reset
style max-retry-after-slow-recovery-expired fill:#dcfce7,stroke:#22c55e,color:#14532d
style check-dock-degraded-new fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-dock-breaker-for-dock-charging-state-new fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-breaker-restore-dock-status-new fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style replace-charger-after-dock-breaker-new fill:#dcfce7,stroke:#22c55e,color:#14532d
style select-charging-alarm-new fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-aircraft-after-dock-charger-clears fill:#dcfce7,stroke:#22c55e,color:#14532d
style select-charging-alarm-legacy fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style charger-fault-status-check-dock-degraded fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style charger-fault-status-escalate-dock-embedded fill:#fef3c7,stroke:#f59e0b,color:#78350f
style unexpected-charge-voltage-escalate-firmware-power fill:#fef3c7,stroke:#f59e0b,color:#78350f
style relay-open-check-dock-degraded fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style relay-open-escalate-dock-hardware fill:#fef3c7,stroke:#f59e0b,color:#78350f
style relay-close-check-dock-degraded fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style relay-close-restart-charger-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style relay-close-escalate-dock-hardware fill:#fef3c7,stroke:#f59e0b,color:#78350f
style failed-to-ramp-check-dock-degraded fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style failed-to-ramp-redock-aircraft fill:#dcfce7,stroke:#22c55e,color:#14532d
style failed-to-ramp-did-redock-resolve fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style failed-to-ramp-inspect-fin-pins-distro fill:#dcfce7,stroke:#22c55e,color:#14532d
style failed-to-ramp-were-issues-found fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style failed-to-ramp-escalate-aircraft-hardware fill:#fef3c7,stroke:#f59e0b,color:#78350f
style failed-to-ramp-create-dock-charger-work-order fill:#dcfce7,stroke:#22c55e,color:#14532d
style charge-timeout-check-dock-degraded fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style charge-timeout-escalate-dock-hardware fill:#fef3c7,stroke:#f59e0b,color:#78350f
style check-dock-health fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style troubleshoot-dock-charging-issue fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-charging-start-after-reset fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-to-service-after-charging-starts fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-firmware-power-after-reset fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-to-firmware-power fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
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.SLOW_CHARGE_RECOVERY_ACTIVE, MAX_RETRY_ATTEMPTS_FAILED if recovery expired, and the related /distro_a.zip_charge_interface alarms around the failed charge-start attempts. Use the alarm that is set at the charge-start failure time you are troubleshooting to choose the next branch.SPN_...), not the mission identifier, so Baraza loads the Dock charging window directly. The plot shows MAX_RETRY_ATTEMPTS_FAILED and the related /distro_a.zip_charge_interface alarms around the failed charge-start attempts. Use the alarm that is set at the failure time to choose the next branch.UNEXPECTED_CHARGER_FAULT_STATUS set, was the Dock in DEGRADED?max_retry_attempts_failed plot.max_retry_attempts_failed plot showing UNEXPECTED_CHARGE_VOLTAGE at the failure time.DOCK_RELAY_FAILED_TO_OPEN set, was the Dock in DEGRADED?max_retry_attempts_failed plot showing DOCK_RELAY_FAILED_TO_OPEN while the Dock was not DEGRADED.DOCK_RELAY_FAILED_TO_CLOSE set, was the Dock in DEGRADED?DOCK_RELAY_FAILED_TO_CLOSE clears.max_retry_attempts_failed plot.FAILED_TO_RAMP_CURRENT set, was the Dock in DEGRADED?max_retry_attempts_failed plot.CHARGE_CURRENT_TIMEOUT set, was the Dock in DEGRADED?max_retry_attempts_failed plot showing CHARGE_CURRENT_TIMEOUT while the Dock was not DEGRADED.DEGRADED, or did the charger service report a charger, relay, or charging-output alarm at the same time?1. Place the Dock into diagnostic mode.
2. Trigger a log offload.
3. Inspect Detailed Dock Status and Alarms.
4. Follow Operations Mode = DEGRADED for the degraded Dock. If Detailed Dock Status shows charger service state
FAULTED_UNRECOVERABLE, follow CHARGER_SERVICE_STATE_FAULTED_UNRECOVERABLE and the charger alarm topic it points to.5. Once the Dock issue is repaired or cleared for retest, power cycle the Aircraft to clear the distro retry counter, then attempt charging again.
max_retry_attempts_failed plot./distro_a.zip_charge_interface.num_failed_handshake_attempts, the SLOW_CHARGE_RECOVERY_ACTIVE alarm report if available, and the max_retry_attempts_failed plot.Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.