Postgres node NDV panel always cuts off / never finishes loading (n8n Cloud 2.31.6)

Questions
, , ,
1

I’m on n8n Cloud, release 2.31.6 (Stable track).

Every Postgres node I open has its NDV (node detail panel) fail to render
completely — see attached screenshot. The Output panel on the right just
shows “No o…” / “Exe…” cut off and never finishes loading, even though
the workflow only has 2 nodes total and this Postgres node has never been
executed (no pinned data).

What I’ve confirmed this is NOT caused by:

  • Canvas size / workflow complexity — happens even in a brand-new workflow
    with only 2-3 nodes total (see screenshot: “Upsert Song” → “Insert Run”).
  • Node content / pinned data — happens on a completely empty Postgres node
    with no prior execution and no pinned data at all.
  • Output payload size — I already reduced the columns returned via
    options.outputColumns to just 4 fields (visible in the screenshot);
    no change in the panel behavior.

What I’ve already tried, none of which fixed it:

  • Hard refresh
  • Fully closing the tab and opening a new one
  • Switching the instance’s release channel from Beta to Stable + restart
    (this was a legitimate fix on its own, since 2.31.6 is already Stable,
    but it did not fix this panel issue)

I searched the forum/GitHub issues and only found an older, apparently
unrelated fix (NDV params cut off, resolved in n8n 1.76.1) — nothing
matching 2.31.6 specifically.

This happens consistently and only with Postgres nodes — other node types
(Set, IF, Execute Workflow, etc.) render their NDV panels normally in the
same workflows.

Workaround I’m using in the meantime: editing Postgres node parameters via
the n8n API instead of opening the NDV panel in the UI at all.

Would appreciate any pointers — is this a known regression in 2.31.6, or is
there something specific to Postgres node rendering I should check on my
end?

image
image1920×1138 182 KB

2

Hey @Osher_Alon, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@paulo.c, @ria, @Naufal_Fayyadh - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

3

Hi @Osher_Alon
The panel isn’t stuck loading, the output pane is rendering too narrow to fit its own labels, which is why they come out clipped as “No o…” and “Exe…”. Postgres insert and upsert nodes draw the column mapper, so their parameters pane claims more width than a Set or IF node does, and the output pane is what gets squeezed at your current viewport.
Change your display resolution or your browser zoom level, then reopen the node. That is what cleared the same pane sizing behaviour in the report below, and it explains why a hard refresh, a new tab, and the channel switch changed nothing, none of those alter the viewport geometry. It isn’t specific to 2.31.6 either, these pane sizing reports go back several releases.