Skip to content

DeepSpeed ZeRO-3: Cannot partition a param in flight (save)

save_16bit_model() under ZeRO-3 asserts because parameters are still in flight when the save interval is not a multiple of the gradient-accumulation steps.

Quick answer

save_16bit_model() under ZeRO-3 asserts because parameters are still in flight when the save interval is not a multiple of the gradient-accumulation steps.

Reliability#deepspeed#zero-3#checkpoint#inflight-param#save

What this failure is

DeepSpeed ZeRO-3: Cannot partition a param in flight (save) is a Reliability failure seen during ML training runs. save_16bit_model() under ZeRO-3 asserts because parameters are still in flight when the save interval is not a multiple of the gradient-accumulation steps. Common tags: Deepspeed, Zero 3, Checkpoint, Inflight Param.

Live diagnosis, no signup

Is this what broke your run? Paste your log.

You're reading about DeepSpeed ZeRO-3: Cannot partition a param in flight (save). Paste your own crash log or traceback below and get the real root cause for YOUR run, not this generic entry. No account, no card. Logs are masked at ingress and never saved to account history.

training_logs.txt
No log to hand? Try one:

3 free diagnoses/day

Want 14 days on the Scale plan?

Request an evaluation code. A verified workplace organization activates up to 50 diagnoses a day, alerts, history, and follow-up questions. No credit card or automatic subscription.

Evaluate one incident

Why it happens (the mechanism)

Save_16bit_model() lacked the save_checkpoint_prologue() call that save_checkpoint() has. Prologue partitions all parameters before saving. Without it, some params remain INFLIGHT and the partition assert fires. Taken together, these mechanisms explain why the failure is reproducible, why it tends to surface on specific workloads or scales, and why generic mitigation attempts often fall short without addressing the underlying cause.

What you'll observe

  • Checkpoint save crashes under ZeRO-3
  • Happens in save_fp16_model / save_16bit_model
  • Save interval not aligned to grad accumulation

Common symptoms and what they mean

SymptomWhy it happens
AssertionError: Cannot partition a param in flightsave_16bit_model() lacked the save_checkpoint_prologue() call that save_checkpoint() has
Crash in _zero3_consolidated_fp16_state_dict()Prologue partitions all parameters before saving
save_16bit_model in the stack traceWithout it, some params remain INFLIGHT and the partition assert fires

Which systems are affected

  • DeepSpeed ZeRO-3
  • Large models (e.g. T5-11B)
  • save_interval % grad_accumulation_steps != 0

How to confirm this is the problem

Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.

  • Reproduce the failure from a clean checkpoint/seed: the symptom must appear without warm-up state from a previous run.
  • Verified signal present: AssertionError: Cannot partition a param in flight
  • Verified signal present: Crash in _zero3_consolidated_fp16_state_dict()
  • Verified signal present: save_16bit_model in the stack trace
  • A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.

The fix and the prevention pattern

The root cause is on this page and stays free. A free account adds the exact remediation steps, saved history, and the fix on every entry in the encyclopedia.

Sign up free. Unlock the full analysis

No credit card. Daily allowance follows verified trust tier. Instant access.

Diagnose this failure in VS Code

Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.

Install the free VS Code extension

DeepSpeed errors in context

DeepSpeed changes when parameters, gradients and optimizer state are created, partitioned, gathered and offloaded. The hub separates ZeRO, memory, checkpoint and pipeline failures by lifecycle phase.

Compare every deepspeed error side by side

Root cause

  • save_16bit_model() lacked the save_checkpoint_prologue() call that save_checkpoint() has
  • Prologue partitions all parameters before saving
  • Without it, some params remain INFLIGHT and the partition assert fires

The fix and how to prevent it

Evaluate Denpex on your own logs

Request a Scale evaluation code. A verified workplace organization activates 14 days with up to 50 diagnoses a day. Every account keeps its current diagnosis allowance and gets a verification path. No card or automatic subscription.

We send a single-use code tied to that address. Static provider and TLD rules do not reject valid addresses. Account trust determines the benefit after signup.

Don't just read the fix, diagnose your run

The encyclopedia tells you what went wrong. Denpex tells you what went wrong in YOUR training run. With your logs, your config, and your stack.