Multi-Task Learning Conflict
Multi-task learning conflicts arise when tasks have different scales, gradients, or learning dynamics that destabilize training.
Multi-task learning conflicts arise when tasks have different scales, gradients, or learning dynamics that destabilize training.
What this failure is
Multi-Task Learning Conflict is a Data Pipeline failure seen during ML training runs. Multi-task learning conflicts arise when tasks have different scales, gradients, or learning dynamics that destabilize training. Common tags: Multi Task, Gradnorm, Pcgrad, Training Stability.
Is this what broke your run? Paste your log.
You're reading about Multi-Task Learning Conflict. 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.
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.
Why it happens (the mechanism)
Task losses at different scales (BCE vs L1). Gradient conflict between tasks. No task weighting or uncertainty weighting. Naive loss sum without balancing. 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
- Some tasks improve while others regress
- Loss is dominated by one task
- Model performs well on average but poorly on individual tasks
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| Task weights cause imbalance | Task losses at different scales (BCE vs L1) |
| Per-task gradients conflict | Gradient conflict between tasks |
| Multi-task loss is unstable | No task weighting or uncertainty weighting |
Which systems are affected
- Multi-task learning
- Multi-head models
- Transfer learning with multiple objectives
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: Task weights cause imbalance
- ✓Verified signal present: Per-task gradients conflict
- ✓Verified signal present: Multi-task loss is unstable
- ✓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 analysisNo 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 extensionRelated failures to investigate next
Root cause
- Task losses at different scales (BCE vs L1)
- Gradient conflict between tasks
- No task weighting or uncertainty weighting
- Naive loss sum without balancing
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.
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.