Stuck objective diagnosis
Zero Company Mission Not Progressing? Diagnose a Stuck Objective
A stuck Mission is not always a bug. Most of the time the current Objective is waiting for a condition that has not happened yet — a required enemy, a required Operator, a specific interaction, or a Mission state that has not been reached. This page checks that first, and only calls something a softlock once every verified condition is satisfied and the Mission still will not advance.
The rule this page diagnoses by
A Mission is only “softlocked” after the verified Objective conditions are satisfied and the expected next Mission state still fails to occur.
Expected behaviour — the Mission is waiting for a condition that has not happened yet.
Missing requirement — a required target, Operator, interaction or Mission state is still incomplete.
Possible softlock — every verified condition is satisfied and the Objective still did not advance.
Start here
Where Is the Mission Stuck?
Pick the one that matches what you see. None of them is a diagnosis yet — each one decides which conditions get checked first.
Mission won’t start
The Mission is on the board but will not begin
Not a softlock. A Mission that will not start is missing a recorded prerequisite, and the requirement is printed on the Mission page.
Objective won’t update
You did the thing the Objective asked for
The most common report, and the most common answer: the Objective is waiting on a target, a state or an interaction that has not finished yet.
Enemy or target is missing
A required enemy, VIP or device is not on the field
The Objective still names a target, but the target is not there. Check the trigger before calling it a spawn bug.
Interaction doesn’t appear
The console, terminal or door gives no prompt
A missing prompt and a missing interaction are not the same thing. Check the Objective, the object and the range before assuming a lock.
Enemy turn won’t end
The AI is still thinking and control never returns
A short delay can be processing. A repeated or indefinite enemy-turn lock is a different problem, and this page routes it.
Objective complete but Mission won’t finish
Every Objective looks closed and the Mission is still running
Usually a secondary condition: an extraction requirement, a required unit, or a pending transition.
I don’t know which one
You are not sure what the Objective is even asking for
Start with the Mission selector below. It prints the Objective, the recorded conditions and the expected next state.
First check
Are You on the Right Troubleshooting Page?
Three neighbouring problems route away from this page, and taking the wrong one wastes a session.
The Mission never appeared at all
Nothing is stuck yet — the Mission is not available. That is an unlock requirement, not a Mission state.
Mission database →It used to be available and now it is gone
The campaign advanced. Expiry and mutually exclusive branches are the campaign working as designed.
Mission Expiration →The Mission is open and you are stuck inside it
You are in the right place. Pick the Mission and the Objective below and the page will check what it is waiting for.
Stay on this page
Baseline
Current troubleshooting baseline — Patch 1.1
Mission troubleshooting must start with the build. Patch 1.1 is the latest official patch this page has seen, and it fixed several combat-state issues — which is exactly why an old symptom and a current symptom need different answers.
Version check
Documented as fixed in your build
This matches an issue documented as fixed in Patch 1.1. If it still reproduces on that build, it no longer matches the documented behaviour and is worth reporting as a current issue.
Patch: 1.1 — released September 9, 2026
Official update checked: September 20, 2026
Mission records indexed: 24 · Objective records: 152
What the page can see
- Observed issue records: 5 (3 player-reported, 2 officially fixed)
- Mission requirements, Objective order and Operator records
- Official patch status for the current build
- Deliberately not available: your save, your turn state and your platform logs
“This Objective requires X.”
“X has not happened, so the Mission is probably waiting for X.”
“The publisher fixed this behaviour in Patch 1.1.”
“Other players have reported this exact Objective getting stuck.”
Main tool
Mission State Diagnostic
Pick the Mission, pick the Objective that is open, then answer a few state questions. The page prints what that Objective is expected to require, and what it is probably waiting for.
Objective router
What Kind of Objective Is Stuck?
Different Objective types have different conditions. The diagnostic swaps its questions by type, and this is the same router it uses.
Eliminate
A required enemy still counts as alive- 1. Any hostile target left on the field?
- 2. Does target cycling or the camera still find one?
- 3. Is the Objective counter still incomplete?
- 4. Is a reinforcement wave or a special target still pending?
- 5. Is a target stuck somewhere unreachable?
“Nothing on screen” is not the same as “nothing left”. A hidden, unreachable or spawn-blocked unit keeps this Objective open.
Interact
The console, terminal or object will not respond- 1. Is the Objective that names this object the active one?
- 2. Is it the exact object the Objective names?
- 3. Is the acting unit inside the interaction range?
- 4. Is a specific Operator required?
- 5. Is the prompt missing even though the object still responds?
No prompt does not always mean no interaction. If every condition is verified, select the object directly before assuming a lock.
Reach
A destination does not register- 1. Have the required units actually reached the destination, not just the leader?
- 2. Does the Objective name a specific unit or Operator?
- 3. Is the destination marker still active?
- 4. Is a gate or transition still pending?
Reach conditions are usually per-unit rather than per-squad. One unit left outside keeps the Objective open.
Protect
A defended target keeps the Objective open- 1. Is the protected target still alive and in play?
- 2. Is the protection duration still running?
- 3. Has the target left the required area?
- 4. Is the next Objective expected right after this one?
A protect Objective closes on the target’s state, not on the enemies you killed around it.
Survive
Survival turns will not resolve- 1. How many survival turns are still shown?
- 2. Has the counter reached its final turn?
- 3. Did the final enemy turn finish after the counter hit zero?
- 4. Is the game still animating a transition?
Survival turn accounting changed in Patch 1.1. Read the version module before treating this as a current issue.
Escort
The escorted unit does not count as arrived- 1. Is the escorted unit still alive and with the squad?
- 2. Has the escorted unit — not only the squad leader — reached the destination?
- 3. Is the escorted unit unable to move?
- 4. Is a conversation or transition still pending?
An escort Objective is bound to the escorted entity. It does not close on the squad’s position alone.
Escape
Extraction will not complete- 1. Are all required Operators inside the zone?
- 2. Is a specific VIP, Droid or escort unit also required?
- 3. Is any required Operator Downed or outside the zone?
- 4. Are all conditions satisfied and the Mission still running?
Extraction requirements are per-unit. “The leader is in the zone” is not the same as “every required unit is in the zone”.
Wait
A waiting Objective has not finished waiting- 1. Does the Objective show a remaining duration or turn count?
- 2. Is the counter still above zero?
- 3. Is the game still processing a transition?
A wait Objective is expected behaviour until its counter finishes. This is the one case where “wait a little longer” is a real answer.
Other
The Objective does not fit a known type- 1. Have you done exactly what the Objective text asks for?
- 2. Did anything change after that action?
- 3. Is any earlier Objective still open?
- 4. Is a cinematic or forced action pending?
The Objective text is still the best source. The diagnostic treats an unclassified Objective as a plain condition check.
Eliminate → count the remaining targets, including the ones you cannot see.
Interact → check the Objective, the object and the range before assuming a lock.
Reach / Escape → check every required unit, not only the leader.
Protect → the target’s state decides, not the enemies around it.
Survive → read the version module before calling the turn accounting wrong.
Escort → the escorted entity has to arrive itself.
Category 1
Objective Won’t Update
The most reported problem, and the one most often answered by reading the Objective properly.
- 1. The Objective did not change.
- 2. Did the required action actually finish? If not, the Mission is still waiting for it.
- 3. Is another target or state still active — a reinforcement, a second Objective, a pending turn?
- 4. Did the game process the final action? Animations and transitions count.
- 5. Only if the last action was processed and nothing moved is this a state-transition softlock.
This is why the page never answers a stuck Objective with a fix list first. Two of the five steps above are conditions, one is a wait, and only the last one is a fault.
High-frequency pattern
Eliminate All Enemies Stuck
This is the single most reported softlock shape, and it is also the easiest one to misread.
A required enemy still counts as alive
- 1. Any hostile target left on the field?
- 2. Does target cycling or the camera still find one?
- 3. Is the Objective counter still incomplete?
- 4. Is a reinforcement wave or a special target still pending?
- 5. Is a target stuck somewhere unreachable?
Player-reported softlock pattern
A remaining unit may exist but be unreachable or stuck behind a spawn area.
Reported by multiple players: a Droid caught inside an enemy spawn door, which cannot be targeted, so the last kill of an eliminate-all Objective can never happen.
Do not read this as a kill count
“Nothing on screen” is not the same as “nothing left”. Before calling it a lock, check the remaining target count, any spawned-but-hidden target, the reinforcement state, a required special target, and whether an escorted or allied unit is counted differently.
Overwatch is not a general fix for a stuck Objective
In one specific report, a player eventually reached a spawn-blocked enemy by repeatedly using Overwatch. In the same discussion another player states that their remaining unit was not a valid hostile target at all, which is why Overwatch could not help them.
So this page does not recommend spamming Overwatch. It is a community observation from one case, not a repair step.
A remaining enemy is stuck behind a spawn door and cannot be targeted
PLAYER-REPORTEDMultiple players report a Droid caught inside an enemy spawn area, keeping an eliminate-all Objective permanently open.
- Objective
- Eliminate all enemies
- Reported on
- 1.1
- None identified
Category 2
Required Enemy or Target Is Missing
A target that has not spawned and a target that cannot be reached are different problems, and the Objective text is the same in both.
Check the trigger first
- • Did the previous Objective actually close?
- • Has the required area been entered?
- • Has the required enemy wave been cleared?
- • Has the conversation or cinematic finished?
What this page will not invent
If the production data names a target but does not record how that target is triggered, the page prints the target and says the exact spawn trigger is not exposed by the current guide data. It will not invent “walk to the north-east corner”.
The Objective text, the required prior step and the required targets are printed in the diagnostic above. Anything past that is a recorded fact or it does not appear on this page.
Category 3
Interaction Doesn’t Appear
Consoles, terminals, doors and datapads all fail in the same familiar order, and the first three checks are conditions rather than faults.
The console, terminal or object will not respond
- 1. Is the Objective that names this object the active one?
- 2. Is it the exact object the Objective names?
- 3. Is the acting unit inside the interaction range?
- 4. Is a specific Operator required?
- 5. Is the prompt missing even though the object still responds?
No prompt is not automatically no interaction
A player report describes reaching Access the Data Downlink with the normally expected interaction prompt missing, while selecting the console directly still allowed the Mission to continue.
That is a specific interaction pattern with evidence behind it, not a licence to click everything on the map.
The expected interaction prompt did not appear on the console
PLAYER-REPORTEDA player report from after Patch 1.1 describes reaching Access the Data Downlink with no normally expected prompt, while selecting the console directly still allowed the Mission to continue.
- Mission
- Enemy Intelligence
- Objective
- Access the Data Downlink
- Reported on
- 1.1
- None identified
Category 4
Extraction / Escape Won’t Complete
Extraction is a per-unit condition. This is the section that turns “my Mission is stuck” into “a required unit has not reached the exit”.
Extraction will not complete
- 1. Are all required Operators inside the zone?
- 2. Is a specific VIP, Droid or escort unit also required?
- 3. Is any required Operator Downed or outside the zone?
- 4. Are all conditions satisfied and the Mission still running?
Two causes, two answers
Rule problem: a required unit has not reached the exit. The Mission is not stuck — go and get it.
Technical cause: a required unit cannot act at all. Players have reported units that started a Mission with no AP, which also affected the enemy AI on the same turn.
The second one is a combat-state problem rather than a route problem, and telling the player to “just move the unit” would be wrong.
Reach and escort conditions work the same way: Reach conditions are usually per-unit rather than per-squad. One unit left outside keeps the Objective open. Survival turn accounting changed in Patch 1.1. Read the version module before treating this as a current issue.
Category 5
Mission Won’t End
Every visible Objective looks closed and the Mission is still running. That is a completion-state question rather than an Objective question.
- 1. Is the current Objective actually complete, or only its visible part?
- 2. Is there a secondary Objective that was never surfaced?
- 3. Is there a survive or escape requirement still running?
- 4. Is a required Operator or unit outside the required zone?
- 5. Is an enemy, target or reinforcement still technically active?
- 6. Is an enemy turn, cinematic or forced action still pending?
Only when all six are clear does this page treat it as a completion-state softlock. Steps 3 and 4 are the two that most often explain the report on their own.
Category 6
Enemy Turn Won’t Finish
This sits next to the crash and freeze category, and the distinction matters: an enemy turn that never returns is a state problem, not an Objective problem.
Check in order
- • Is the game still animating or thinking?
- • Does control return after a short wait?
- • Does it happen at the same trigger every time?
- • Did a reaction shot or an Overwatch action get queued just before it?
A short delay and a lock are not the same
A short delay can sometimes be processing. A repeated or indefinite enemy-turn lock is a different issue: reports range from a recovery after some seconds to no recovery after ten to fifteen minutes.
So this page does not say an enemy turn always resolves itself. It says a repeatable lock is worth recording.
A Coil Captain kept trying to heal an already-dead target after an Overwatch kill
FIXED IN PATCH 1.1This was a turn-order processing fault: the combat action was not processed correctly, which is what stalled the turn order.
- Reported on
- 1.0
- Patch 1.1 fixed the combat action processing and the resulting turn-order behaviour.
The final Mission stops after a scripted action, or the AI turn never ends
PLAYER-REPORTEDSeveral independent reports describe the final Mission becoming unresponsive after control is taken from the player and the enemy turn never returning.
- Mission
- The Infinite Coil
- Reported on
- 1.1
- None identified
Category 7
Scripted Transition Won’t Continue
Forced actions, control hand-offs and cinematic transitions are where a repeatable script problem is easiest to describe and hardest to dismiss.
Check in order
- • Did a cinematic or forced action just trigger?
- • Did control return to you afterwards?
- • Did the next Objective appear?
- • Does the same trigger reproduce it on every reload?
Reproducible script softlock
Players report the final Mission becoming unresponsive after control is handed to Fathom, and separately an AI turn that never finishes. That is a repeatable script trigger rather than a random freeze, and the report should say so.
Version
Patch 1.1 Mission Fixes
A fixed issue and a similar-looking issue are different verdicts. This is what each one actually covers.
Combat actions not processed correctly
FIXED — PATCH 1.1An action did not resolve, or a turn-order step stalled afterwards
The patch notes list combat actions not being processed properly, and the turn-order fault that followed from it.
Current build: On the current build an action is expected to resolve and the turn order to continue.
This does not mean every Mission softlock was fixed. Mission-specific reports still exist after the patch.
Coil Captain healing a dead target
FIXED — PATCH 1.1A Captain kept acting after its target was killed by Overwatch
An Overwatch kill left the Captain attempting to heal a target that was already dead, which broke the turn order.
Current build: The action is expected to be processed and the turn to continue.
An Overwatch report that is not this exact pattern is a different problem and is not covered by this fix.
Tel-Rea Hero Mission survival turn
FIXED — PATCH 1.1The final battle ended with 1 survival turn remaining
The survival Objective resolved early instead of after the final enemy turn.
Current build: The final battle is expected to resolve after the last enemy turn.
If it still reproduces on Patch 1.1, it no longer matches the documented fixed behaviour and is a current issue again.
Various crashes and stability issues
FIXED — PATCH 1.1Crashes and stability faults reported across the campaign
The patch shipped a batch of crash and stability fixes rather than one named mission fault.
Current build: Stability reports continued after the patch, so identify the point where it happens.
A crash is a different category from a stuck Objective. Crashes route away from this page.
Patch 1.1 fixed several combat-state issues, but mission-specific player reports still exist after it. That is exactly why this page asks for the build and the symptom before it says anything about a fix.
Tool
Mission-Specific Issue Search
Search a Mission or an Objective and this reads the observed-issue overlay plus every published Objective record.
Type at least three characters. The search reads the observed-issue overlay and every published Objective record.
After a possible softlock
Safe Recovery Steps
Low-risk first, always. Nothing here is worth a campaign save.
In order
- 1. Give the state a short moment — only if the AI or an animation is still processing
- 2. Open and close the pause menu, which is harmless and sometimes refreshes a stuck state
- 3. Reload the latest checkpoint or autosave if your campaign mode supports it
- 4. Restart the current Mission from the Mission start if the game allows it
- 5. Confirm you are on the latest patch
- 6. On PC, repair or verify the game files through the store you launched from
- 7. Capture the reproduction and report it through official support
Boundary
Community reports vary about what clears a stuck state, and one player’s workaround is not a general fix. Nothing on this page should be read as a guaranteed repair, and no step here is worth losing a campaign save over.
Restricted saves
Beskar / Single-Save Precautions
A restricted-save run does not have the same rollback flexibility, so the recovery order changes.
Preserve → Diagnose → low-risk retry → official support
A restricted-save run does not have the same rollback flexibility as a standard campaign. Players have reported facing a softlocked run with a single save and no comfortable way back.
- • Preserve the current save before attempting advanced troubleshooting
- • Do not delete, move or overwrite save files as a general fix
- • Do not disable cloud sync as a first move — it can remove the copy you wanted to keep
- • Report the state rather than experimenting with files
What to send instead
Record the Mission, the Objective, the build and the exact action before it stopped. A preserved save and a clear description are worth more than any file-level experiment, and they are the two things this page can actually help you produce.
Next step
Prepare a Mission Bug Report
The report builder above pre-fills the Mission and the Objective once a possible softlock is identified. This is the shape of a report somebody can act on.
- • Mission and Objective, named exactly
- • Platform and build
- • The last action before it stopped
- • Expected behaviour versus what happened
- • Whether it reproduces on every reload or every Mission restart
- • A screenshot or clip if you have one
Reproducibility changes the priority of a report, but this page never turns it into a bug probability. “Every Mission restart” is a stronger report than “once”; neither is a percentage.
FAQ
Mission Not Progressing Questions
Why won’t my Mission progress in Zero Company?
Usually the current Objective is waiting for a condition that has not happened yet: a required enemy, a required Operator, a specific interaction, or a Mission state that has not been reached. Check the Objective text first, then the recorded conditions, and only treat it as a softlock when all of them are satisfied and the Mission still will not advance.
Why isn’t my Objective updating?
An Objective stays open while any of its conditions are unresolved. That includes a remaining enemy, a target that has not spawned, an earlier Objective that is still open, and an interaction that has not been processed. Walk those in order rather than replaying the Mission.
Why won’t my Mission end?
A finished Objective is not the same as a finished Mission. Extraction requirements, required units, secondary Objectives, a pending enemy turn and a closing transition can all keep it running.
Why can’t I find the last enemy?
Something can still count as a remaining target without being on screen. Check target cycling and the camera, and check whether a reinforcement or a special target is still pending. If a unit exists but cannot be reached or targeted, that is the pattern this page treats as a possible softlock.
Why is an enemy stuck behind a door?
Players have reported a Droid caught inside an enemy spawn area, keeping an eliminate-all Objective open. That is a player-reported pattern rather than an officially confirmed bug, and it leaves the Objective permanently incomplete because the unit cannot be targeted.
Why won’t the interaction prompt appear?
A missing prompt is not automatically a missing interaction. Verify the active Objective, the exact object and the interaction range first. In one post-patch report the prompt was absent while selecting the console directly still continued the Mission.
Why can’t I interact with the console?
Check that the Objective naming that console is the active one, that it is the exact object the Objective names, and that the acting unit is inside the interaction range. If all three hold and the prompt is missing, try the object directly before assuming the Mission is locked.
Why won’t extraction complete?
Extraction conditions are checked per unit. Every required Operator has to be inside the zone, and a VIP, Droid or escort unit may be required as well. A Downed unit cannot satisfy the condition.
Why won’t the enemy turn end?
A short delay can be processing. A repeated or indefinite enemy-turn lock is a different problem: note whether it reproduces at the same trigger and whether a reaction shot or an Overwatch action was queued before it.
Why is the AI stuck thinking?
The enemy turn either resolves or it does not. If it never returns control, record the Mission, the last action and whether it happens every time — that is the detail a report needs.
Why didn’t the next Objective appear?
The next Objective depends on the current one closing first. If a cinematic or forced action was triggered, the state may simply still be in transition. A repeated failure at the same trigger is the scripted-softlock pattern.
Is my Mission softlocked?
Only if every verified condition for the current Objective is satisfied and the expected next Mission state still fails to occur. Anything short of that is a condition, a wait or a prompt problem, and the diagnostic above says which one.
Should I restart the Mission?
Restarting is a low-risk step, but it is not the first one. Confirm the conditions, check the build, and preserve the save in a restricted-save run before you restart anything.
Can I reload a checkpoint?
Where your campaign mode supports it. In a Beskar or other restricted-save run, do not load an older save to test a fix — that can cost more progress than the stuck Objective did.
What should I do in Beskar mode if a Mission is stuck?
Preserve the save, avoid file-level actions, check the build, and report the state. The order on this page is Preserve, Diagnose, low-risk retry, then official support — never delete a save as a general fix.
What Mission bugs were fixed in Patch 1.1?
Patch 1.1 fixed combat actions not being processed correctly, the Coil Captain turn-order fault after an Overwatch kill, the Tel-Rea Hero Mission final battle ending early with one survival turn remaining, and a batch of crash and stability issues. Mission-specific player reports still exist after the patch.
How do I report a reproducible Mission bug?
Send a report with the Mission, the Objective, your platform, your build, what you did, what you expected, what happened, whether it reproduces on every reload, and any capture you have. The report builder on this page pre-fills the Mission and Objective for you.
Related troubleshooting
Where to Go Next
Fix stuck missions and objectives in STAR WARS Zero Company. Check required enemies, interactions, Operators, mission states and triggers, then identify whether the problem is an unmet condition, delayed game state or possible softlock.