Quick answer: Call Run Behavior Tree from the AI Controller, ensure at least one task returns Running for ongoing actions, and check that the Blackboard and root are set.

A Behavior Tree only advances while running and while a task holds the Running state. Starting it and keeping a task in progress fixes a frozen tree. Here is how.

How to fix it

1. Run the tree from the controller

In the AI Controller's OnPossess or BeginPlay, call Run Behavior Tree with the asset. Without this, the BT asset exists but never executes.

2. Return Running for ongoing tasks

A custom task that does continuous work must call Finish Execute later and stay Running in between. If every task returns Succeeded immediately, the tree races to completion and idles.

3. Verify Blackboard and decorators

A missing Blackboard asset or a decorator that always aborts can prevent the tree from selecting any branch. Confirm the Blackboard is assigned and decorator conditions can pass.

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 Unreal Engine 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.