By the way, in our production environment we have multiple frontend servers and in our testing environment only one. I'm not sure how the load balancing works, but could it be that frontend server 1 handles the first event and another frontend server handles the second one? So the events are handled at the same time and the second event finishes quicker because it contains less code?

We ran some tests and turned out we were right. Not sure if it's because of multiple frontend servers, but the events were sent in the correct order but the second event was handled before the first was finished.

thanks for sharing, Ramon.

I tried an experiment based on your post, and was actually amazed to see that the events run one after the other.

I intuitively would have expected for them to each run asynchronously, meaning that it is perfectly possible for fast ones to finish before slow ones.  But they don't, the second one fires only starts after the first one is handled.

Can you share a bit more, like screen prints of your firing and handling event flows, and any other things that are at play such as updating input parameters or refreshing data actions, that could play a role in why in production it suddenly worked differently.  

I'm not really convinced about the number of front-end servers playing a role, as I think all the event firing and handling happens on the device of the end user (unless of course data get refreshed somewhere in your flow)

Dorine

All this is pure curiousity, so I understand if you don't have time and just want to get on with it, no worries.