I’m doing some testing and it appears that this is only occurring in my behavior tree that was converted from 4.0.2, and not in a new tree that I created in 4.1 (so I guess I could work around this issue unless it shows up again later).
It also appears to have something to do with the contents of the custom service blueprint. Removing certain parts of the event graph in my service blueprint stops the issue from occurring. The same applies to a new service blueprint I’ve just created - copying my old service’s event graph into the new service causes the error, but removing certain parts of it resolves it.
I haven’t determined yet exactly which nodes are the problem, but it’s somewhere in this graph:
