Hello James_Stephens, thank you for asking. I might be able to help answer this question.
That screenshot just shows a minor n8n UI bug. When you see an execution with a runtime of -2s, it usually means the execution started, but the system didnt record the start and finish timestamps correctly. This also can happen occasionally if your server clock isn’t perfectly synchronized or if the workflow crashed/stopped before n8n could finalize the metadata. It doesnt affect the workflow logic itself, just the way its displayed in the Executions list.
There are a few things that i can suggest to you to fix this:
Make sure the server has NTP (time sync) enabled, so timestamps dont drift.
If you’re using the cloud version, you can ignore it.. its just a display glitch.
If the execution is stuck in “Running“ forever, click Stop and re-run to clear it.
Thats all i can suggest. I hope your problem can be resolved.