# UE 5.8 StateTree: A State with Tasks all marked as not affecting completion may incorrectly complete as Succeeded 

**URL:** <https://forums.unrealengine.com/t/ue-5-8-statetree-a-state-with-tasks-all-marked-as-not-affecting-completion-may-incorrectly-complete-as-succeeded/2740370>\
**Category:** Issues and Bug Reporting (Unreal Engine)\
**Tags:** unreal-engine\
**Created:** [August 3, 2026, 2:58pm UTC](https://forums.unrealengine.com/t/ue-5-8-statetree-a-state-with-tasks-all-marked-as-not-affecting-completion-may-incorrectly-complete-as-succeeded/2740370 "2026-08-03T14:58:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![unlimited\_007](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@unlimited\_007](https://forums.unrealengine.com/u/unlimited_007)\
**Post date:** [August 3, 2026, 2:58pm UTC](https://forums.unrealengine.com/t/ue-5-8-statetree-a-state-with-tasks-all-marked-as-not-affecting-completion-may-incorrectly-complete-as-succeeded/2740370/1 "2026-08-03T14:58:22Z")

</div>

### Summary

In UE 5.8 StateTree, if a State:

1. has at least one Task;
2. all Tasks are configured as not affecting State completion, i.e. `Considered for Completion = false`;
3. the State’s completion type is `Any`;
4. the Task keeps returning `Running` after `EnterState` and never calls `FinishTask`;

then under some runtime conditions the State may still be evaluated as `Succeeded` shortly after entering. This triggers completion transition evaluation. If the State has no completion transition, StateTree falls back to Root and interrupts a still-running child State.

This does not necessarily reproduce on every Play. The compiled StateTree asset only defines the completion mask / bit layout; it does not store the current completion status. The current status is stored in a reusable runtime `ActiveTasksStatus` bit buffer. If the synthetic bit is currently 0, the State may temporarily behave as `Running`. If that bit has been polluted by previous state or previous runtime logic as `Succeeded`, and `ResetStatus()` fails to clear it, the State appears completed immediately after entering.

Local debugging indicates the issue is caused by a mismatch between the UE 5.8 `MakeCompletionTasksMask()` synthetic completion bit and runtime `ResetStatus(State.TasksNum)`:

- `MakeCompletionTasksMask()` inserts an extra synthetic completion bit when there are no considered tasks;
- `FStateTreeTasksCompletionStatus::Push()` still calls `ResetStatus(State.TasksNum)`;
- when `TasksNum > 0` and all tasks are not considered, the synthetic bit is placed after the real task bit(s);
- `ResetStatus(State.TasksNum)` clears only the real task bit(s), not the synthetic bit;
- if the synthetic bit remains `Succeeded`, the whole State is incorrectly evaluated as completed.

### What Type of Bug are you experiencing?

AI

### Steps to Reproduce

1. Create or open a UE 5.8 project.

2. Create a StateTree.

3. Create a structure like this:

4. Add a StateTree Task to `ParentState`, for example a Blueprint Task:

5. Set the Task’s `Considered for Completion` / `Toggle Completion` to disabled, so it does not affect State completion.

6. Set `ParentState` completion type to `Any`.

7. Do not configure a completion transition on `ParentState`.

8. Let the StateTree enter `ParentState.ChildState`.

9. Observe the StateTree runtime behavior.

### Expected Result

When a State has Tasks but all of them have Considered for Completion = false:

- those Tasks should not drive the State to completed;
- if there is no other explicit State-level completion source, the State should remain Running;
- while a child State is still Running, the parent State should not become Succeeded due to a stale synthetic completion bit;
- StateTree should not fall back to Root via completion fallback.

### Observed Result

The parent State may be evaluated as Succeeded even though:

- its only Task returns Running;
- that Task is explicitly configured as not affecting State completion;
- the child State is still Running.

When this happens, StateTree tries to find a completion transition for the parent State. If no completion transition exists, StateTree triggers the internal fallback:  
“Could not trigger completion transition, jump back to root state.”  
Internal → Root

This interrupts the still-running child State.

The symptom may be intermittent. If the reused ActiveTasksStatus runtime bit buffer does not currently have the synthetic completion bit polluted, the State may behave normally. If the synthetic bit remains Succeeded, the State is incorrectly treated as completed immediately after entering.

### Affects Versions

5.8

### Platform(s)

Android  
iOS  
Linux  
Mac  
OpenXR  
visionOS  
Windows

### Upload an image

 ![StateTree_TaskCompletionMistake.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/9/a/a9af8e476c2c9e6189c4040bc1cc87aa8c8812a4.png) ![code_clearfunc_notmatched.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/4/3/7/4372886eedbcabbc5c72ccb1aab1796176c800bd.png) ![code_compiler_changed.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/9/6/b/96ba9f13e0044e52aec88af1bf861bf067a01994.png)

---

<div class="post-metadata">

**Author:** ![James.Keeling](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@James.Keeling](https://forums.unrealengine.com/u/James.Keeling)\
**Post date:** [August 19, 2026, 4:10pm UTC](https://forums.unrealengine.com/t/ue-5-8-statetree-a-state-with-tasks-all-marked-as-not-affecting-completion-may-incorrectly-complete-as-succeeded/2740370/2 "2026-08-19T16:10:34Z")

</div>

I believe we have this fixed in UE5 main stream, but it has not made it into the 5.8 release. Here is a link to the GitHub commit I believe should fix this problem: [GitHub Link](https://github.com/EpicGames/UnrealEngine/commit/71b807f41310a603478f5a958d05a93dbf95cecb). This change has some header file changes, so it will not make a hotfix release.

-James

---

<div class="post-metadata">

**Author:** ![Doddzilla0](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Doddzilla0](https://forums.unrealengine.com/u/Doddzilla0)\
**Post date:** [October 7, 2026, 6:52pm UTC](https://forums.unrealengine.com/t/ue-5-8-statetree-a-state-with-tasks-all-marked-as-not-affecting-completion-may-incorrectly-complete-as-succeeded/2740370/3 "2026-10-07T18:52:30Z")

</div>

The issue tracker [https://issues.unrealengine.com/issue/UE-384337](https://issues.unrealengine.com/issue/UE-384337) states that it is fixed, targeting 6.0. However, I’m wondering if that should actually say 5.9, given that we have a confirmed 5.9. It would be great to get that fix before 6.0.

---

<div class="post-metadata">

**Author:** ![James.Keeling](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@James.Keeling](https://forums.unrealengine.com/u/James.Keeling)\
**Post date:** [October 19, 2026, 1:50pm UTC](https://forums.unrealengine.com/t/ue-5-8-statetree-a-state-with-tasks-all-marked-as-not-affecting-completion-may-incorrectly-complete-as-succeeded/2740370/4 "2026-10-19T13:50:34Z")

</div>

The change was made in UE6 main before we had any thoughts towards a possible 5.9. I will see what I can do to get it included for 5.9 or moved into UE5 main at the least.

-James

---

<div class="post-metadata">

**Author:** ![GPBF](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@GPBF](https://forums.unrealengine.com/u/GPBF)\
**Post date:** [November 13, 2026, 11:49pm UTC](https://forums.unrealengine.com/t/ue-5-8-statetree-a-state-with-tasks-all-marked-as-not-affecting-completion-may-incorrectly-complete-as-succeeded/2740370/5 "2026-11-13T23:49:29Z")

</div>

very blasé attitude towards a major game breaking bug, mate.
