If Overwatch is not working in Star Wars Zero Company, update to Patch 1.2 before retesting a clean cone. EA's October 15 update includes additional trigger and coverage fixes. That is a publisher report, not a guarantee for every encounter. The Patch 1.1 details and community reports below describe the earlier version.
Before treating every failed Overwatch as a bug, separate three different situations: the reaction attack never triggers, the reaction attack triggers but misses, or the attack lands and the enemy keeps moving. Only the first case is the strongest sign that the system failed to process the trigger correctly.
Jump to the Patch 1.2 Overwatch fixes.
What Patch 1.2 fixes with Overwatch
Checked October 16, 2026: EA's Patch 1.2 notes, published October 15, describe the specific fixes below.
| Symptom | Publisher-reported fix |
|---|---|
| No reaction attack | Cones failing to trigger and invisible coverage zones. |
| Misleading cone | Displayed coverage where geometry blocks the shot, and enemy cones starting from the wrong position. |
| Activation or interface problems | Further fixes to Overwatch activation and its UI. |
Record your installed version when investigating a remaining problem. Earlier 1.1 reports do not establish that the same failure persists in 1.2.
What Patch 1.1 fixed with Overwatch
Patch 1.1 contains multiple Overwatch-specific fixes. EA says it corrected cases where reaction shots could fire through solid objects at Operators the attacker could not see, cases where Overwatch triggered on a unit outside the targeting cone, and several situations where enemies or Operators were attacked unintentionally. It also fixed a turn-order problem involving a Coil Captain attempting to heal a target that Overwatch had already killed.
The same tactical-combat section includes a broader fix for combat actions not being processed correctly. That matters because some launch-week reports described combat sequences hanging, resolving in the wrong order, or skipping expected reactions when several actions happened close together.
These changes make Patch 1.1 important for anyone relying heavily on reaction fire, but the patch notes stop short of saying that all Overwatch trigger failures are resolved. If your game is still on an older build, update before troubleshooting further. See our Patch 1.1 breakdown for the wider list of fixes.
How Overwatch is supposed to work
EA's combat guide describes Overwatch as a reaction system used during the enemy turn. You place a targeting area, commit the Operator to Overwatch, and the Operator automatically attacks when an enemy moves through or takes an action inside that area. Activating it immediately ends that Operator's turn, so it is usually best used after movement, attacks, or support actions that you want to complete first.
StarWars.com's getting-started guide gives the same basic rule: spend the Operator's remaining action points to hold position for a reaction attack, then punish an enemy that moves or acts inside the selected zone during the opponent's turn.
That definition gives you the simplest diagnostic test. If the enemy clearly enters the cone or performs an action while already inside it and no reaction attack begins at all, the behavior does not match the normal rule described by EA.
Overwatch did not trigger at all
Community reports following Patch 1.1 described enemies running directly through visible Overwatch zones without a shot beginning, including cases with several Operators covering the same path. Similar reports mentioned Droidekas and late-game Coil units apparently ignoring multiple cones during the same encounter.
Those reports and PC Gamer's post-1.1 observations predate Patch 1.2. They document earlier behavior and should not be presented as confirmation that the same bugs persist after 1.2.
If you can reproduce the problem, note the mission, enemy type, number of overlapping Overwatch zones, whether the enemy was entering the battlefield as reinforcement, and whether another reaction or ability was resolving at the same time. Those details are more useful for identifying a real trigger bug than simply recording that an attack missed.
The shot triggered but missed
A miss is different from Overwatch failing to activate. Overwatch is still an attack and does not automatically mean the target will be hit. If the camera shifts into the reaction sequence, the Operator fires, and the attack misses, then the trigger itself worked.
The targeting area and positioning still matter. Do not place the largest possible cone simply because it covers more ground. Use a lane the enemy is likely to cross and keep the Operator in a position with a clean line of sight. If the objective allows it, shorter and more controlled firing lanes are easier to reason about than a huge zone with several pieces of cover and multiple moving enemies.
Patch 1.1 also fixed the separate bug where attacks displaying a 100% chance to hit could still miss. That fix improves the reliability of the displayed combat numbers, but it should not be confused with a guarantee that every Overwatch shot has a 100% hit chance.
The enemy was hit but kept moving
An enemy continuing to move after an Overwatch attack is not automatically evidence that Overwatch failed. EA describes Overwatch as a tool that can help interrupt movement, not as a guaranteed movement stop every time a reaction attack occurs.
This distinction is important because players often describe two very different events as "Overwatch not working." If the reaction attack visibly fires and damages the target, the trigger worked even if the enemy completes part or all of its movement afterward. A true no-trigger problem looks different: the enemy crosses or acts inside the zone and the reaction sequence never begins.
Late-game enemy traits and campaign upgrades can also change how reliable a defensive plan feels. Inspect the enemy and review active campaign modifiers before assuming that every unusual result is a technical bug.
Overlapping Overwatch zones can make the problem harder to read
Many player reports involve several Operators covering the same enemy path. That is also a strategy the developers themselves highlighted before launch: multiple Overwatch zones can be placed around reinforcement areas to punish incoming enemies.
In practice, overlapping reactions can make it harder to see which Operator triggered, which shot was consumed, and whether the next enemy action should have caused another response. Patch 1.1 fixed multiple cases involving unintended targets and reaction ordering, which suggests that dense chains of reaction attacks were one of the areas being actively corrected.
If you are trying to determine whether your current problem is a bug, test the same kind of movement with a single clean Overwatch cone instead of four overlapping zones. If one Operator repeatedly fails to react to an enemy moving through the center of a clear cone, that is easier to identify than a complicated chain involving several reaction attacks, reinforcements, retaliation effects, and abilities.
Practical troubleshooting after updating
There is no official universal workaround for the remaining no-trigger reports, but you can reduce how much a failed reaction costs your turn.
First, update to Patch 1.2 and restart the game after the update has finished installing. Second, place Overwatch over a clear route rather than the edge of several possible paths. Third, avoid building an entire turn around one reaction shot when a dangerous enemy can immediately reach a vulnerable Operator if the trigger fails. Keep direct damage, control, displacement, or cover as backup options.
Forced movement is also an intentional tactical interaction. EA has specifically highlighted pushing or pulling an enemy into a squad member's Overwatch zone as a supported strategy. When available, displacement can create a more deliberate trigger opportunity than waiting for enemy pathfinding to choose the route you expected.
If one encounter appears permanently stuck in a bad combat state, restarting the mission is also a reasonable test. The official getting-started guidance confirms that missions can be restarted with the same Operators. A repeated failure under the same simple conditions is stronger evidence of a persistent bug than a one-off sequence in a crowded fight.
Should you avoid Overwatch in Beskar mode?
Overwatch is still a core combat mechanic, but players using Beskar mode should be more conservative about depending on it as the only thing preventing a squad wipe. Beskar campaigns remove some of the safety available in a normal run, so an inconsistent reaction mechanic carries more risk.
Patch 1.1 separately fixed Beskar save disappearance and a Beskar crash issue, which makes the mode safer than it was at launch. Even so, if your current campaign repeatedly reproduces an Overwatch no-trigger problem, use direct control and guaranteed positioning tools for critical turns instead of assuming a reaction will protect the squad.
FAQ
Is Overwatch completely fixed in Patch 1.2?
EA lists specific trigger, cone, and interface fixes in Patch 1.2. The notes do not promise that every Overwatch problem is resolved.
Why did an enemy walk through my Overwatch after being shot?
The reaction attack triggering and the enemy's movement being interrupted are separate outcomes. If the shot fired, Overwatch activated. Continuing movement does not by itself prove the trigger was bugged.
Why did nothing happen when an enemy entered the cone?
A no-trigger case is different from a shot missing. Confirm Patch 1.2 is installed, test a clean single cone, and record the mission, enemy, and game version if the failure repeats.
Does Overwatch end my Operator's turn?
Yes. EA's combat guide states that activating Overwatch immediately ends that Operator's turn, so use other desired actions before committing to it.