Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix 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. [1 comments, 2 participants]

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…
GitHub stats
n8n-io/n8n#28372•Fetched 2026-04-13 05:45:24
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
davidwork8489davidwork8489
Participants
davidwork8489davidwork8489n8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

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 f025a786 (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

extent analysis

TL;DR

Downgrade to n8n version 2.13.4 to regain immediate visibility of preceding node outputs in the NDV while a workflow is paused on a Wait node.

Guidance

  • The issue is caused by a regression introduced in version 2.14.0, which persists execution data to the database at the Wait boundary, leaving the UI without data to display until execution resumes.
  • To verify the issue, follow the provided steps to reproduce, which involve creating a workflow with a Wait node and checking the NDV output panel while the workflow is paused.
  • Consider downgrading to version 2.13.4 as a temporary workaround until a fix is available in a future version.
  • Be aware that downgrading may introduce other compatibility issues or remove features added in later versions.

Example

No code snippet is provided as the issue is related to a version regression rather than a code-specific problem.

Notes

The provided debug information and version details suggest that the issue is not related to the specific database, execution mode, or hosting environment, but rather to the change introduced in version 2.14.0.

Recommendation

Apply workaround: Downgrade to version 2.13.4, as it is the last known version where the expected behavior was observed, allowing for immediate visibility of preceding node outputs in the NDV while a workflow is paused on a Wait node.

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

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.

#cache error#pipeline error#runtime error#dependency conflict#environment 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