n8n Dashboard showing 0 executions despite successful database records (Queue Mode)
Anonymous
HOBBYOP

2 months ago

I am encountering a persistent issue where the n8n "Overview" dashboard (Production executions, Failure rate, etc.) remains at zero, even though workflows are running successfully and executions are being recorded in the database.

Context:

  • Platform: Railway

  • Mode: Queue Mode (Primary + Worker + Redis + Postgres)

  • n8n Version: 2.2.3 (latest stable)

What I have tested so far to isolate the issue:

  1. Existing Project: Cleaned up the database and redeployed. History is being populated, but the dashboard stays at 0.

  2. New Instance (Data Import): Created a fresh n8n project on Railway, imported my previous data into a clean structure. Same result: 0 executions on the dashboard.

  3. Clean Slate (No Data): Created a third, completely fresh instance with no data import at all. I set up a simple production workflow (triggering every 30 seconds). On that instance, the exectution count moved up.

Observations:

  • In the 2 first cases, the Execution History list correctly shows the runs with status "Success" and incrementing IDs.

  • The execution_entity table in Postgres is being updated correctly by the worker.

  • The workflows are "Active" (Production mode), not manual runs.

  • Environment variables for Postgres and Redis are verified and communication between services is working.

  • Timezones (GENERIC_TIMEZONE) are consistent across services.

It seems like the aggregation query used by the n8n dashboard is failing to retrieve or count the data, even though the raw execution data exists. Since this happens even on a completely fresh Railway template/install without any legacy data, I'm wondering if this is a known issue with how n8n interacts with Railway's networking or specific Postgres/Redis configurations in Queue mode.

Has anyone encountered this "zeroed" dashboard issue recently? Any lead on where to look in the logs for the dashboard aggregation process?

Solved$10 Bounty

0 Replies

Status changed to Awaiting User Response Railway 2 months ago


Status changed to Solved Anonymous 2 months ago


Loading...