Describe the problem/error/question
Hi. I have a separate database for the workflow results, and I keep a column called run_index there for my jobs. This value only increments by one when I restart the relevant workflow.
When I check the total number of executions I’ve used last week, the n8n UI shows 38,815, while in my database I see 19,320 (sum of run_index). A few other workflows (maybe 3–5) have also been running, but no matter what, the total never reaches 38,815.
In my workflow, I have 2 trigger nodes. One is start, the other is restart. Depending on the situation, only one of them is called, never both. They just happen to have similar paths:
v1/analyst/start- immediately response
v1/analyst/restart- immediately response
I separated them this way because they need different parameters.
Could the reason why the total execution count in the n8n UI is roughly double the total in my database be that I have 2 trigger nodes, even though I only call one of them? In this setup, I also call a sub-workflow. It was stated somewhere that sub-workflows don’t count toward executions. Could something be going wrong here?
What is the error message (if any)?
I am using n8n main node metrics to track what is going on, and here is my prometheus query for visualization. (n8n_scaling_mode_queue_jobs_completed ) I have a single environment right now (production).
sum by(environment) (
last_over_time(
n8n_scaling_mode_queue_jobs_completed{
service="n8n",
service_type="main",
environment="$environment"
}[$interval]
)
)
Here is the Insight section.
Information on your n8n setup
- n8n version: 1.106.3
- Database (default: SQLite): PostgreSQL
- n8n EXECUTIONS_PROCESS setting (default: own, main): queue mode & on-premise
- Running n8n via (Docker, npm, n8n cloud, desktop app): GKE
- Operating system: Linux