Instead of tracing, or a foor loop for all actors of class…
A proper (best practice) would be to add a gameplay tag to the actors when they spawn in, then loop the actors with that game-play tag to check a distance.
Tags are accessible via the string array variable Tags.
Though, you may need to edit the actor’s class in CPP to make the variable available, this I do not recall…
The loop should be less expensive than a multi trace - when dealing with high number of actors/items that react to the trace.