Got some errors where the flow had a weird error which I have to figure out. But the time of the error keeps changing. It is the current time that is shown. Makes it tricky to find out what was going on when the error happened.
I believe such a behaviour might take place when the n8n instance crashes. Once recovered, the UI could depict the executions that were interrupted during the crash in this weird way.
Thanks, that is a good point. Will have a look into that.
But still it should not do this in the UI as the created and stopped timestamps are saved according to the API.