n8n shows two active workflows, but only one is in use

[Fank]

Bug Description

Following view shows two active workflows:

But when I filter the overview for active it shows only one:

Also running workflows export shows me one active workflow:

~ $ n8n export:workflow --all --pretty --output=exportall.json
Invalid timestamp value for N8N_RELEASE_DATE: $(date -u +"%Y-%m-%dT%H:%M:%SZ")
User settings loaded from: /home/node/.n8n/config
Successfully exported 58 workflows.
~ $ ls
exportall.json
~ $ cat exportall.json | jq -c '[.[] | select(.active == true)] | length'
1

But for what ever reason this workflow, still creates execution like if it is still active:

Which informations do you need?
You can also contact me in discord (username: Fank), its maybe faster for research.

Debug info

core

• n8nVersion: 1.82.1
• platform: docker (self-hosted)
• nodeJsVersion: 20.18.3
• database: postgres
• executionMode: scaling
• concurrency: -1
• license: enterprise (production)
• consumerId: 03176d77-824f-4ef2-83db-39f7bc022c2f

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: s3

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/134.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-03-11T09:06:59.241Z

To Reproduce

no clue

Expected behavior

Show the correct amount of active works as when i filter for active workflows in overview.

Operating System

docker (self-hosted)

n8n Version

1.82.1

Node.js Version

20.18.3

Database

PostgreSQL

Execution mode

queue

[Joffcom]

Hey @Fank,

We have created an internal ticket to look into this which we will be tracking as "GHC-1141"

[Fank]

I talked with @Joffcom on discord, he recommended disabling the workflows on all main nodes and enable it again.
This so far caused to an increase of 1, now overview is correct with 2 but 3 workflows are in use:

[Fank]

The json entry for "Chat Agent" from n8n export:workflow shows "triggerCount": 2, but the workflow itself does only have one trigger node.

[Joffcom]

@Fank reproduced the issue and I have raised it internally to find out which team is best suited to resolve this.