When a story is started, a story run GUID is created. This is a unique identifier for that story run. For each action that is executed, they have an event ID, which is unique to the singular execution of that action.

An Explode action treats however many events were emitted from it almost as different story runs. So, they're emitted and they can flow through the rest of the story in parallel to each other, but they maintain the same story run GUID.

We do not respect the order of the events from an Explode. For example, when these events are submitted, if you run the same transformation against 50 events and then use an Implode action, the Implode can and will receive them out of order. This is because, on our back-end, some processors will do the same job slightly faster than others, and while we process as first in/first out, we can't guarantee that an Implode will be in the same order as it was sent out.