Within StopTree() OnTaskFinished is called but AbortTask is not. It seems like it should also be aborted? I know OnTaskFinished is a recent addition so maybe some of the base tasks simply haven’t been updated with expected behavior.
You’re right, task should receive some meaningful notification about stopping tree and abort is best choice. I’ll enter new feature request for modifying StopTree to work with latent abort calls.
Alright sounds good. I use multiple trees and have been running into issues due to the lack of cleanup via abort on certain tasks.