Yes, I promoted it to try to destroy it manually because of the behavior I explained. And about the Theme variable not updating, I just called the same widget from another blueprint, and from there it does update. Both caller blueprints have the same hierarchy, actually, the second one is a modified duplicate of the first one, and I pass the same parameters on the same events (inherited) to create the tooltips. I still have the debug output of them being in memory, but I don’t care (for now) as long as they update the Theme, but the first one still doesn’t.