The Python state doesn't always include a createdAt timestamp for tool-call messages in a conversation entry. (in .NET testing that it consistently did include those properties.) The dashboard should accommodate that, however, as they're not supposed to be required--I'll make a fix.

That said, the behavior where the tool call appears "completed" after a subsequent request is due to the Python state suddenly having createdAt properties for old messages when the new state is added. Also, the createdAt properties of the conversation entries themselves are being changed, serialized with a more recent timestamp. I think this is a deserialization-serialization issue in the Python logic.