Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix import:entities Data Tables "error fetching data table content"

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

When moving from sqlite to postgresql using entities:export and entities:import, Data Tables fail to work. The data tables are are listed in the UI, but when viewing the data tables themselves, they are empty and an error appears similar to:

Error fetching data table content

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

When moving from sqlite to postgresql using entities:export and entities:import, Data Tables fail to work. The data tables are are listed in the UI, but when viewing the data tables themselves, they are empty and an error appears similar to:

Error fetching data table content relation "data_table_user_xxxxx" does not exist

Additionally, even newly created data tables are unusable in workflows with nodes reporting that the table cannot be found. This functionally renders data tables completely unusable. All other functionality appears to have been migrated successfully.

I was able to reproduce the issue multiple times.

<img width="353" height="308" alt="Image" src="https://github.com/user-attachments/assets/a06a3400-64a1-4320-938d-7320b5ac4497" />

To Reproduce

  1. Using n8n in a single container running sqlite, run: n8n export:entities --outputDir=./exports --includeExecutionHistoryDataTables

  2. Using a multicontainer n8n deployment with a fresh postgresql, run: n8n import:entities --inputDir=./exports --truncateTables

Expected behavior

The expected behavior is that all system information is migrated from the sqlite-backed n8n instance to the postgresql-backed n8n instance.

Debug Info

Debug info below for the sqlite deployment.

Debug info

core

  • n8nVersion: 2.19.5
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 5b2fa78c-d65a-4a04-b046-35fdf01a5292

storage

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

pruning

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

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10.15; rv:150.0) gecko/20100101 firefox/150.0
  • isTouchDevice: false

Generated at: 2026-05-08T20:11:58.711Z

Operating System

Rocky Linux 8.10 with Docker Swarm

n8n Version

2.19.5

Node.js Version

whatever comes with the container

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The expected behavior is that all system information is migrated from the sqlite-backed n8n instance to the postgresql-backed n8n instance.

#search optimization#API routing#API middleware#SSR setup#ISR setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING