Ah, I see.
So, as explained earlier, the eventInfo is not part of the computed state. This is an issue I previously raised with the developer of the extension that there is no real way to use the extension to access eventInfo data.
instead, use a custom code block and do a (note the ?. construct w...