Since v2.14.0, when a workflow contains a **Wait node**, the output data of all preceding nodes is not visible in the execution UI until the entire execution completes.

[davidwork8489]

Bug Description

Since v2.14.0, when a workflow is paused on a Wait node, the output of preceding nodes is not visible in the NDV. In v2.13.4 it was immediately accessible. The regression was introduced by commit f025a78 (PR #27066), which removed the in-memory execution path for short waits and now persists all execution data to DB at the Wait boundary — leaving the UI with nothing to display until the execution resumes.

To Reproduce

Steps to reproduce

1. Create a workflow: Manual Trigger → Postgres (SELECT query) → Wait (5s) → Set
2. Execute manually
3. While paused on the Wait, click the Postgres node to open the NDV

Expected behavior

Expected: Query results are visible in the NDV output panel.

Actual: No output is shown. Data only appears after the Wait resumes and the full execution completes.

Debug Info

Debug info

core

• n8nVersion: 2.13.4
• platform: docker (self-hosted)
• nodeJsVersion: 24.13.1
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: community
• consumerId: unknown

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

security

• secureCookie: false

Generated at: 2026-04-12T15:02:13.906Z

Operating System

Docker

n8n Version

2.15.x

Node.js Version

Any

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

[n8n-assistant]

Hey @davidwork8489,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-7707".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-7707

[Dinhmanh96]

Same issues

[RicardoE105]

Could not replicate the issue with what we have in master right now. I did not use a postgres node, but a set node instead. Can you try again in the latest version to see if you can replicate it still?

[davidwork8489]

2026-04-23.08-23-09.mov

Just see the attached video. Version is 2.18.1, but while waiting, no other nodes show output data. This is important because previous node can define "when free the wait node"

[davidwork8489]

Hello, I just tried version 2.19.2 and the issue is fixed!

[nikhilkuria]

Thanks for confirming @davidwork8489