Why does my SetTrigger seem to do nothing?

Triggers are consumed at the next animator update. If multiple transitions out of the current state can fire, the higher-listed one wins and consumes the trigger. A self-loop with Can Transition To Self enabled often eats the trigger before the real transition fires.

What does Has Exit Time do?

With Has Exit Time on, the transition can only fire after the current animation has played past the Exit Time fraction of its length. With it off, the transition fires the instant the trigger condition is true. For instant responses (jump, hit reaction) turn it off; for animation-locked moves leave it on.

How do I debug transition order?

Open the Animator window with the GameObject selected and Play running. The active state highlights and you can watch transitions fire. Reorder transitions by dragging in the list; higher-listed transitions are evaluated first.

Fix: Unity Animator State Transition Skipped with Can Transition To Self

Quick answer: Disable Can Transition To Self on any state with self-looping transitions, set Has Exit Time = false on instant transitions, and reorder transitions so the most specific condition is evaluated first. Triggers only fire on the highest-priority matching transition.

SetTrigger(“Jump”) returns. The animator does not jump. The Idle clip restarts, mid-animation, like a hiccup. Or the trigger fires twice and the player tries to jump twice. Every Unity dev hits this once; the cause is almost always the self-transition rule and one of two settings.

The Symptom

SetTrigger calls a state change that visibly does not happen. Or fires the wrong state. Or fires once after the right state already plays. Behavior depends on which animation frame the trigger lands on, which feels random.

What Causes This

Animator transitions are evaluated top-down within a state. A trigger condition that matches more than one outgoing transition consumes on the first match in list order. Subtle gotchas:

Can Transition To Self — if a self-transition with the same condition exists, it fires first and the trigger never reaches its intended target.
Has Exit Time = true — the transition is gated until the clip has played past Exit Time. Triggers fired earlier are still consumed but cause no visible change.
Trigger reset — SetTrigger sets the trigger; the next evaluation that doesn’t match consumes it. If your transition has a parameter condition that’s false, the trigger is consumed silently.

The Fix

Step 1: Disable Can Transition To Self everywhere. Click the state. In Inspector → State → Transitions, expand each transition and uncheck Can Transition To Self unless you specifically want a re-trigger to restart the same animation.

Step 2: Has Exit Time = false on instant transitions. Click the transition arrow. In the Settings panel uncheck Has Exit Time. The transition now fires the moment the trigger is set, regardless of clip progress.

Step 3: Set Transition Duration explicitly. A duration of 0.25 is reasonable for most humanoid moves; 0 for snappy responses (hit, parry). Default 0.25 is often fine but the field is in normalized time of the source clip if Fixed Duration is off — flip Fixed Duration on and the value is in seconds, which is what you almost always want.

Step 4: Reorder transitions. Specific conditions first, generic last.

// Idle state's transition list, in order:
1. Idle -> Hit       (Trigger: Hit)         // most specific, fires first
2. Idle -> Jump      (Trigger: Jump)
3. Idle -> Run       (bool: IsRunning)
4. Idle -> Idle      (none, default loop)  // last, never blocks others

Code Side

Set the trigger only when the animator is in a state where it can be consumed. ResetTrigger before a SetTrigger if you suspect a stale trigger:

public void Jump()
{
    animator.ResetTrigger("Jump");
    animator.SetTrigger("Jump");
}

Verifying

Open the Animator window with the player selected during Play. Trigger the action; the active state should jump to the target visibly. If the source state restarts instead, your self-transition is winning. If nothing changes, your trigger is being consumed silently — check the transition’s parameter conditions.

Understanding the issue

Animation systems blend pose data over time. The blend math is straightforward; the timing isn't. State machines, transition curves, layer weights - each compounds with the others.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Disable self-transitions. Exit time off for instant. Order transitions specific-first. Triggers land where you intended.”

Related Issues

For animation not playing at all, see animation not playing. For animator events not firing, see animation events.

Self-transition off. Exit time off. Specific first. The Animator obeys.