n8n - 💡(How to fix) Fix Supabase Drops Table Selection

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

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

When using the next/previous node icons from within the node window to navigate to a Supabase node, that Supabase node drops the selected table and related field names which need to be reselected. It doesn't do this when closing and opening a different node window directly, only navigating from within the node window.

To Reproduce

  1. Establish at least 2 nodes, one of which is Supabase
  2. Enter Supabase table details with field info
  3. Navigate away from Supabase node from within node window and then navigate back.

Expected behavior

As described above

Debug Info

core

  • n8nVersion: 2.20.7-exp.0
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: f787c87b-798e-4f0b-a013-b1661ac2bb7c

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 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/148.0.0.0 safari/537.36
  • isTouchDevice: false

cluster

  • instanceCount: 1
  • versions: 2.20.7-exp.0
  • instances:
    • instanceKey: ac5a9432-313a-4c35-b94d-62771223188c, hostId: main-f4836ab65a45, instanceType: main, instanceRole: leader, version: 2.20.7-exp.0
  • checks:
    • check: hostid-clash, status: succeeded, warnings: -
    • check: lifecycle, status: succeeded, warnings: -
    • check: split-brain, status: succeeded, warnings: -
    • check: version-mismatch, status: succeeded, warnings: -

Generated at: 2026-05-16T14:41:24.385Z

Operating System

Ubuntu 24.04.3 LTS (GNU/Linux 6.8.0-111-generic x86_64)

n8n Version

n8n Version2.20.7-exp.0

Node.js Version

24.14.1

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

As described above

Still need to ship something?

×6

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

Back to top recommendations

TRENDING