I’ve run into what looks like a debug issue. I have the debug setting “automatically expand most recent message” turned on, but the newest message isn’t actually being expanded. Based on the timestamps in the attached screenshot, it’s opening an older message instead.
I’m guessing with those message timestamps being so close together, that they were sent in a batch through the debug stream and that we are not sorting those properly in the UI, as they are not guaranteed to be in to-the-millisecond timestamp order in the array that comes over the stream. Thanks for pointing this out.
Today’s platform update includes a minor adjustment to the debug log that should ensure the messages received in a batch are sorted by timestamp - which should resolve the issue you raised here. Thanks for bringing this to our attention.