Bug with Supabase Node

[Nate922SE]

Describe the problem/error/question

Bug.
Supabase5 node is bugging. Can not remove, move or anything.

When I tried to delete it, the node did not disappear. It only lost the connections to other nodes. When I tried to go back, a new node was created (I now have one extra node). Now this new node is somehow connected to the old, supabase5 node. Bc when I tried to move/delete etc the Supabase5 node now, all the actions applied to the node I got back after I tried to go back.

What is the error message (if any)?

none

Screen.Recording.2025-02-16.at.13.55.52.mov

Please share your workflow/screenshots/recording

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Debug info

core

• n8nVersion: 1.67.1
• platform: npm
• nodeJsVersion: 20.18.0
• database: sqlite
• executionMode: regular
• concurrency: 5
• license: community

storage

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

pruning

• enabled: true
• maxAge: 168 hours
• maxCount: 2500 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/133.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-02-16T12:21:56.057Z}

[Joffcom]

Hey @Nate922SE,

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

[Joffcom]

Hey @Nate922SE

I have not seen that before, could you first update n8n and see if that helps if it doesn't can you export the workflow and share it here so we can a look?

when exporting the workflow make sure it doesn't contain any api keys or secrets