Bug Description

When N8N is run in queue-mode the execution data (public.execution_data."data") isn't deleted from the database after the finished execution regardless of the settings (server-environment or in the workflow itself).

To Reproduce

1. Start docker-compose with N8N in queue mode
2. Change settings of workflow to not safe any execution data
3. Execut workflow and confirm finished execution
4. Check Database for execution data, example: docker exec -it postgres psql -U n8n -d n8n SELECT “executionId”, pg_column_size(“data”) FROM public.execution_data;

Here is a minimal docker-compose example which can reproduce the problem:

demo workflow.json docker-compose-n8n.yml n8n-task-runners.json .env.demo.txt

Expected behavior

public.execution_data."data" should have only "[]" in the executions where the execution data was disabled.

Debug Info

Debug info

core

• n8nVersion: 2.18.5
• platform: docker (self-hosted)
• nodeJsVersion: 24.14.1
• nodeEnv: production
• database: postgres
• executionMode: scaling (single-main)
• concurrency: 10
• license: community
• consumerId: unknown

storage

• success: none
• error: none
• progress: false
• manual: false
• binaryMode: database

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/147.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2026-04-30T07:07:04.732Z

Operating System

Rocky Linux 9.7 (Blue Onyx)

n8n Version

2.18.5

Node.js Version

v22.22.2

Database

PostgreSQL

Execution mode

queue

Hosting

self hosted