Bug? Floating error message out of touch with reality

[Sandman]

This is a really small bug, but still worth to report, I suppose. I should also point out that I've never noticed this before, so I probably hit some kind of very small edge-case.

I was renaming the method a CallSub called, and noticed that the error message didn't display the correct value. The same was true for the log (not displayed in the image). I'm not sure if it's relevant to finding the bug, but neither the method I had as a value before editing nor the new one (in the image) existed yet.

 

[Erel]

Did it fix itself after a few seconds?

 

[Sandman]

I didn't really hang around, so I don't know. But I checked now (renaming the askHiredBy first to something else to cause an error) and it seems to have solved itself, yes.