Asynchronous Event Flows - What's the Solution?

We basically just keep the account ID is a as an attribute on everything that happens. It can be potentially a little tricky if you do two things back to back that both invoke the same kind of very asynchronous event based flow in that we don't have a great mechanism for something like a request ID. And it's one of the things that we've been sort of looking at and thinking on, but for the most part just by nature of how the architecture works and the design, there aren't a lot of cases where you would be in a position to do that right. They're all kind of joined by this common key of user ID that we can still use to filter and group.