A dispatcher broadcast from inside a handler does not see later bindings
A Blueprint Event Dispatcher calls its bindings in registration order unless removals have reordered the list: ProcessMulticastDelegate iterates a copy from front to back. When one handler broadcasts another dispatcher, only bindings already registered with that dispatcher are included. Bindings added by later handlers do not exist yet. In this example, registration order follows from the lifecycle phases in which the Bind Event to... nodes run across different Blueprints.