Skip to content
File

NVIDIA: diagnosis and recovery of AI training jobs

This dossier follows NVIDIA's tools for diagnosing failures and restarting AI training across machines, including their limits.

Last updated : 1 key moments

Where things stand

On 2 November 2026, NVIDIA detailed Recovery and Attribution. The tools address complementary functions; effectiveness depends on available telemetry and checkpoints.

NVIDIA details open tools for diagnosing and restarting AI training

NVIDIA presented Recovery and Attribution on 2 November 2026, two open tools for teams running AI training across multiple machines. The former coordinates recovery; the latter investigates why workloads failed.

Rear of a server rack.
Server rack at NERSC in 2011. Archive illustration; not a NVIDIA deployment. D. Coetzee, CC0; resized. — D. Coetzee / Wikimedia Commons — CC0 1.0 https://creativecommons.org/publicdomain/zero/1.0/ ; NERSC, 14 octobre 2011, taille réduite.

Recovery detects interruptions, classifies problems, excludes implicated machines and recommends restarting or stopping a job under configured policies. A restart uses the training program's latest checkpoint: the tool does not recreate progress lost without a checkpoint.

Attribution correlates logs, metrics and scheduler state to separate an initiating cause from cascading errors. NVIDIA says diagnosis depends on the quality of collected evidence and can remain ambiguous.

The published recovery timings are NVIDIA's internal measurements. They describe initiation of an action, without guaranteeing the full time until productive training resumes.

Sources 4