I think one has to be very careful about throwing away the wrapping ExecutionException when logging - it must be logged somewhere or we lose essential information. For example, we'll lose the stacktrace of who called the effector in the first place.

Agree that the current logging is extremely verbose and hard to read for end users (but its completeness is useful for developers during debugging). I haven't yet run this to see exactly what it looks like...