Error in Execution and the execution time is the current time

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.

image
image

from API:

Information on your n8n setup

  • n8n version: 1.84.3
  • Database (default: SQLite): Postgres
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu
1 Like

Hello @BramKn,
Could you please provide a workflow that can be used to reproduce the error?

1 Like

Hi @mk_n8n

I cannot really reproduce it, but I have seen it a couple of times already. The error is an unknown error that doesn’t tell me anything on the error.

anything in debug logs? might help :slight_smile:

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.

1 Like

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.

Hey @BramKn , we have an internal ticket raised for this issue. Though, it’s been blocked for a few months now. I have pinged the team.

1 Like