What causes a Godot AI task stuck on Running?

An async or animation-driven action starts but never reports completion because the finish signal is not connected or the status is never set, so the tree waits on it forever.

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 Godot AI Task Stuck on Running With No Completion Signal

Quick answer: Explicitly return SUCCESS/FAILURE when the action's goal is met, and connect to completion signals (animation_finished, tween finished) instead of assuming the action ends on its own.

A Godot AI that begins an attack or move and then hangs is running an action that never reports done. Wiring its completion signal and returning a terminal status fixes the hang. Here is how.

How to fix it

1. Connect the completion signal

For animation- or tween-driven actions, connect to animation_finished or the tween's finished signal and only then mark the task complete, instead of leaving it Running indefinitely.

2. Return a terminal status

Make the task return SUCCESS or FAILURE once its condition is satisfied; a task that only ever returns RUNNING blocks its parent forever.

3. Add a watchdog timer

Start a timeout when the action begins and force FAILURE if it elapses, so a missed signal cannot wedge the tree permanently.

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 Godot 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 errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.