n8n - 💡(How to fix) Fix wait dont stop [1 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#28498Fetched 2026-04-15 06:44:15
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
Participants
Timeline (top)
cross-referenced ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all

Code Example

(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.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

At the end of the workflow I put a wait of 5s but for some reason it doesn't wait just 5s, it stays for much longer and then n8n itself terminates the process.

What is the error message (if any)?

This execution hasn't finished yet Refresh to see the latest status. More info

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.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.16.0
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: community

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; rv:148.0) gecko/20100101 firefox/148.0
  • isTouchDevice: false

Generated at: 2026-04-15T02:46:32.548Z

extent analysis

TL;DR

The workflow's wait node may not be functioning as expected due to an issue with n8n's timing or an external factor causing the process to terminate prematurely.

Guidance

  • Review the n8n documentation for the wait node to ensure it is configured correctly, as the provided link in the error message may offer insight into potential issues.
  • Check the workflow for any other nodes that could be causing the delay or termination, such as nodes with long-running operations or external API calls.
  • Verify that the docker container and postgres database are functioning correctly and not causing any resource constraints that could impact the workflow's execution.
  • Consider adding logging or debugging statements to the workflow to gain more insight into its execution and identify potential bottlenecks.

Example

No code example is provided as the issue does not include specific code snippets to work with.

Notes

The issue may be related to the specific version of n8n (2.16.0) or the docker and postgres setup, but without more information, it's difficult to determine the root cause.

Recommendation

Apply a workaround by reviewing and optimizing the workflow to minimize potential bottlenecks and adding logging to gain more insight into its execution, as upgrading to a fixed version is not clearly implied in the provided information.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING