Unreal’s hierarchical state machine framework, designed for AI but usable for other state-driven behavior. Tasks run within states; conditions transition between states.

Task starts a long-running operation (timer, latent action) and doesn’t cancel it in ExitState. The op completes after the state has changed, sometimes resurrecting old state behavior.

Override ExitState. Clear any timers via UWorld’s GetTimerManager().ClearTimer. Cancel async ops with stored handles. Mark transient state as invalid.

Fix: Unreal State Tree Task Not Completing on Exit

Quick answer: Override ExitState to clear timers, cancel async handles, and reset transient state. Don’t rely on next-task transitions to clean up previous task’s side effects.

An AI uses State Tree: PatrolState → ChaseState. Patrol task schedules a “say hello” timer; player triggers chase before it fires. The hello plays during chase. Task didn’t cancel its timer.

State Tree Task Lifecycle

EnterState: state activated. Start work.
Tick: per-frame while active.
ExitState: state deactivated. Clean up.
FinishTask: signals task completion (for transitions).

Cancel Timers in ExitState

struct FPatrolTask : public FStateTreeTaskBase
{
    FTimerHandle HelloTimer;

    virtual EStateTreeRunStatus EnterState(FStateTreeExecutionContext& Ctx, const FStateTreeTransitionResult&) override
    {
        UWorld* World = Ctx.GetWorld();
        World->GetTimerManager().SetTimer(HelloTimer, [this]() { PlayHello(); }, 3.0f, false);
        return EStateTreeRunStatus::Running;
    }

    virtual void ExitState(FStateTreeExecutionContext& Ctx, const FStateTreeTransitionResult&) override
    {
        Ctx.GetWorld()->GetTimerManager().ClearTimer(HelloTimer);
    }
};

EnterState starts timer; ExitState cancels it. No straggler effects.

Async Action Handles

Similar pattern for FAsyncAction, FStreamableHandle:

virtual void ExitState(...) override
{
    if (PreloadHandle.IsValid()) {
        PreloadHandle->CancelHandle();
        PreloadHandle.Reset();
    }
}

Idempotent Cleanup

ExitState might be called from various paths (transition, tree reset, owner destroyed). Make cleanup safe to call twice. Use IsValid checks, then null out handles.

FinishTask Discipline

If your task represents finite work (“walk to point”), call Ctx.SetRunStatus(EStateTreeRunStatus::Succeeded) in Tick when done. Otherwise the task hangs and the state never transitions.

Verifying

Transition between states quickly. No leftover behavior from prior state (timers, sounds, animations). Tree debug visualizer shows clean state changes. AI feels reactive.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unreal Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

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

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unreal. 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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Unreal-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

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unreal, 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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

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.

“EnterState starts work, ExitState cleans up. State Tree tasks must own their lifecycle.”

For combat AI especially, leaked timers cause “ghost taunts” or phantom animations after enemy death. Strict ExitState discipline avoids embarrassment.