What causes a behavior tree node stuck on Running in Unity?

The action task only ever returns Running because it never tests its own completion condition, so the parent composite waits on it forever and the AI freezes.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a Behavior Tree Node Stuck Returning Running in Unity

Quick answer: Make the task return Success or Failure once its goal is met or impossible, add a timeout fallback, and verify the condition is reachable each tick.

If an enemy walks up to a wall and just stops thinking, a leaf node is almost always returning Running indefinitely. The tree cannot advance past a child that never reports done. Here is how to find and fix it.

How to fix it

1. Return a terminal status

Every action must eventually return Success or Failure. A MoveTo task should return Success when within an arrival radius and Failure if the path is invalid, not Running on every tick.

2. Add a timeout decorator

Wrap long-running tasks in a timeout decorator that aborts after N seconds and returns Failure, so a stuck node cannot wedge the whole tree.

3. Log the active node

Print the currently ticking leaf each frame. If the same node logs forever, that node owns the bug; inspect why its exit condition is never satisfied (e.g. an arrival check using the wrong distance).

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.