Of the nodes used within the event, only the component visibility change node is slow to respond.
It’s unresponsive the first few times, then completely stops working after visibility is changed.
The other nodes are working so the event is definitely executed.
I don’t know why this happened, it was working fine in the early stages of the project.
Is it because memory usage has increased, or because you changed some graphics settings?
Does anyone know the cause of this?
Extremely unlikely.
My gut feeling tells me it’s Occam’s Razor and, simply, something else also manipulates the components’ visibility. I doubt anyone can deduct much from the tiny snippet and vague description 
Debug it. Breakpoints, Prints and all that Jazz…
It can be more complicated, ofc. Since this is a CAC, the child actor may have their own visibility rules and so on… and so can its components. Who knows how deep the rabbit hole goes.
I spent hours researching this problem.
I then compared a project with and without the problem from a backup.
The results are the same process, different behavior.
The process was working perfectly so I left it alone for a while. It was broken when I noticed it.
Yes, it’s definitely the butterfly effect. Something has happened, but there’s no way to know.