This will probably require a deeper dive into your implementation... Seeing the result here doesn't tell us what is happening.
Could events be overwritten between them being set and when the beacon is sent? I can see there is something blurred out for "link name" so I can see this is an action and not a page view... how are you setting the events? If you are setting them in a separate rule, you should be aware that actions are a bit different from page views....
If you have a bunch of items set in the s.object (i.e. s.prop1, s.prop2, s.eVar1, s.eVar2, events, etc) these will all send when s.t() is triggered...
Now, when we look at the history of how Adobe tracking works (before Launch, before the easy "Clear Vars" action, etc)... the s object would still be set after the page view had been set... when you tracked an action, you needed a way to curate what elements were to be sent on the action...
That came in the form of setting s.linkTrackVars and s.linkTrackEvents.... this is where you pass a list of what elements should be included in in the s.tl() beacon..
So if from above, I wanted prop1, eVar2 and events, I would have to set:
s.linkTrackVars = "prop1,eVar2,events";
s.linkTrackEvents = "event1,events";
In Launch, these variables are set by the Set Variables action.. but if you are using a separate rule to set your events, then are sending your beacon, your s.linkTrackVars may be missing "events" and your s.linkTrackEvents may not be set with the specific events you need to be included.
This would be my first guess as to what is happening, not having seen your code, but based on the behaviour alone.
