From what I understand, Activation event in BT service should fire once when it’s activated.
However, in my case, it works like Tick. It gets triggered continuously.
(I confirmed no task gets aborted during the session)
Is this a known issue?
Or am I wrong about the Activation node?
BT logic called every tick. Your service also would be activated every tick.
I did a test in a clean project(4.13), and the Activation works just as I expected.
Seems like something’s messed up in my project.
As I have no idea what might be causing the problem thus can’t provide further information, I feel obliged to mark this question as resolved and try to figure it out on my own.
Thanks for sharing your thought.
No, it doesn’t.
I made a custom BT Task instead of wait, and below is how it works.
Activation is called only once, whereas Tick is called every .4s ~ .6s. Execute fires every time it finishes execution.
What setting do you have here?
And your activation node fires every 5 seconds?
Do you have finish execution node in your task?
Ok, I found something interesting. If I add a selector between the root and the selector that holds the service, the activation is called every time the execute is called. Please see the image below.
I still don’t know if this is a bug or EPIC’s original intention. 
I should unmark my answer. I hope epic staff have explanation for this.
Activation events trigger when nodes become part of the active subtree. Tick events trigger per given delta seconds as long as the subtree is active. So if the active subtree does not alter path, tick events still get triggered, but activation events will not. That’s my understanding.
