This is by design I'm afraid, and was discussed in another similar thread.
In short creating objects and then using them in subevents is unstable for various reasons, and can cause crashes. So this had to be fixed, and now created objects do not exist until the top-level event finishes. (This is how it always worked in Classic btw, and for the same reason, so it was a bug that C2 has been letting you get away with possibly unstable events.) They are picked in their own subevent, but in subsequent subevents they don't exist yet. It is very difficult to work around this without simply putting it back which results in some projects crashing and not working at all, so I think it has to stay like this instead.
I assume the events you screenshotted are in a subevent, which is important because it affects the result.
The workaround is just to put subsequent subevents nested under the event that created the objects instead, or in this case a subsequent event is not necessary because you can just use the created instance in the same event.