Short answer
First check your exact objective and installed build. Use the 1.0.3 counter checks for Progressive or Passive Challenges. A completed chapter, an in-game challenge and a platform achievement are separate results: identify which one is missing.
Reviewed September 25, 2026: 1.0.3 patch notes and the historical September 17 issue report. Older Steam tips below are community evidence, not confirmed current-build fixes.
Above the new target, but still incomplete?
For a Progressive Challenge already beyond its revised target, the developer says to earn further progress toward that same objective to trigger completion. After Prestige, Passive Challenges can still appear locked while continuing to count; the display fix remains pending.
- Confirm the category and target.Read the current requirement for that exact character or weapon. Do not use an older screenshot's target or substitute a story chapter goal.
- Compare before and after.Capture the counter, perform a qualifying action and let the normal result flow finish. Check the counter and completion state again.
- If nothing changes, preserve the evidence.Keep both screenshots, the build, objective, equipment and match role for the support report. Do not reset progress or delete saves.
Check the named challenge before replaying
For historical story fixes, see 1.0.2. For character challenges and missing trophies, use the version-aware issue list. A changed requirement does not prove that every earlier tracking report is resolved. Nothing here establishes a new Chapter 2 or Chapter 4 route.
Weapon challenge? The September 17 update clarifies that weapon progression requires the corresponding weapon even when the text is ambiguous. Match your equipped weapon to the challenge before judging its counter. For Chapter 2 Challenge 6, use the no-alert objective, not a different chapter's completion rule.
Track the failure precisely
| Symptom | Current reading | Capture next |
|---|---|---|
| Challenge stays incomplete | Needs verification | Exact wording, chapter or mode, difficulty, and the action that should have completed it. |
| Achievement does not unlock | Check the named trophy | Platform, result screen, account state, and whether the linked challenge registered. Compare the open issue list above. |
| Chapter or result restarts | Community report | Chapter, checkpoint, platform, and what appears after closing and reopening the game. |
| Progress appears after leaving | Useful lead | Whether the result was visible before leaving the chapter and whether it persisted after relaunch. |
One clean verification run
- Copy the objective exactly.“Alert nobody,” “kill,” “execute,” and “complete the chapter” are different conditions.
- Start from a clean state.Do not mix a stealth test with a full-clear test when the goals point in opposite directions.
- Finish the result flow.Watch for the completion screen before starting another chapter or closing the game.
- Record the build and platform.A post-patch PC result should not silently become a claim about PlayStation or Xbox.
Steam community save and tracking reports
Steam players repeatedly describe the same save-hygiene checks: finish the score or completion screen, avoid restarting from a late save while testing a challenge, and return to the main menu before closing the game. These are practical reproduction leads, not a guaranteed fix; reports differ by chapter, platform, and build.
Compare the Steam challenges discussion with the separate Chapter Bugs report. Both are player evidence for testing, not an official save specification.
Challenge tracking FAQ
Did patch 1.0.3 fix every challenge?
No blanket completion guarantee is supported. Compare the exact objective, category and counter; a revised target is different from a verified solution to every story challenge.
Why did my story challenge not count?
Possible explanations include a missed wording condition, an incomplete result flow, or a tracking problem. Preserve the exact objective and platform before choosing one explanation.
Should I restart the whole chapter?
Only after recording the failed result. A clean replay can test the condition, but repeating an unrecorded run makes it harder to tell whether anything changed.