n8n - 💡(How to fix) Fix The Wait node never resumes. [2 comments, 3 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#28664Fetched 2026-04-20 12:15:13
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
0
Author
Timeline (top)
commented ×2labeled ×1mentioned ×1subscribed ×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

Describe the problem/error/question

Once the node Wait, starts, even for 1 second, it never ends, it get stucked.

What is the error message (if any)?

In the logs it says: n8n | dbTime.getTime is not a function for each time the wait should "tic".

Please share your workflow/screenshots/recording

I donthave it right now, but it is a never ending Wait.

(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.1
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)

storage

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

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 50000 executions

client

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

Generated at: 2026-04-20T03:19:36.010Z

extent analysis

TL;DR

The Wait node gets stuck due to a JavaScript error dbTime.getTime is not a function, indicating a potential issue with the dbTime object.

Guidance

  • Verify the dbTime object is correctly defined and has a getTime method before using it in the Wait node.
  • Check the n8n version and Node.js version for any known issues or compatibility problems, as the error might be related to the specific versions used (n8n 2.16.1 and Node.js 24.14.1).
  • Inspect the workflow configuration to ensure the Wait node is properly set up and not causing an infinite loop.
  • Consider checking the Postgres database connection and configuration, as the error might be related to the database interaction.

Example

No code snippet can be provided without more context about the workflow and node configuration.

Notes

The issue might be specific to the n8n version, Node.js version, or Postgres database configuration. Further investigation is needed to determine the root cause.

Recommendation

Apply a workaround by checking the dbTime object and its methods before using it in the Wait node, as the error suggests a potential issue with the object's definition or usage.

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