I have a very simple workflow with a Webhook trigger that I use as health-check endpoint to call periodically so I can monitor my server’s status. I’ve recently form v 0.2?? to v 1.14.2 and replaced my MariaDB with a Postgres DB. The Webhook url and uuid is still the same as before as I backed up my flows.
I think the problem here (as with similar cases reported recently) is that the final execution status isn’t written to the database as it should be once the execution finishes. So the execution list fetches an execution with a start date, but no end date and no result from the database, and displays the execution as running. Let’s hope the update fixes the problem for you as well
On a completely separate note, n8n also has a built-in health check endpoint these days at /healthz. So you might no longer need this extra workflow just to check whether n8n is alive. Of course it could make sense to keep the workflow as part of your end-to-end testing approach and to discover issues like this one.
Thanks for sharing some details, interesting! I had a hunch it was just the UI that was confused.
I have 1.15.2 up and running and will let you know how things go either way. I’ll keep my healthcheck workflow running at least to see how it’s doing, but great to hear there’s a built-in option for that now.
I noticed there’s also a metrics endpoint. any way of securing that one? or using that data in a workflow? I actually like the webhooks having a uuid path, which gives some kind of security.