Yes, that is correct @smanjunath211, you would need to mouse-over the debug message to know which read file node was which... however, at least you would know it was a read file node, because at the moment you would see 3342ca1cd3ad053f.
This is also why I suggested adding some colour-coding to part of the message, but even without it, I think showing the node name would be an improvement.
I had raised a feature request some time ago to Auto serialise (if that's a word) the debug nodes as soon as they are dragged on the editor tabs, so that if we need to , we can name them, else still by default they will have unique names. the same can be applied to other nodes as well i suppose. ?
Honestly, when I see node:3342ca1cd3ad053f I have equally no idea which node created the message without hovering over the message, so we're in no worse a position if that message field is populated with the node type when node name is blank.
True! But how many times have you quickly put together a flow to test something? Doesn't make sense to go through an label every node in those instances.