Wait Node not working when Resume parameter is passed as Expression

Describe the problem/error/question

When I try to pass the Resume parameter to the Wait node as an Expression instead of a Fixed value, a " Problem running workflow" error comes up.

What is the error message (if any)?

The workflow has issues and cannot be executed for that reason. Please fix them first.

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.81.4
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own, main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): N8N Cloud
  • Operating system: Idk, its cloud

Debug info>

instance information

Debug info

core

  • n8nVersion: 1.81.4
  • platform: docker (cloud)
  • nodeJsVersion: 20.18.3
  • database: sqlite
  • executionMode: regular
  • concurrency: 20
  • license: community
  • consumerId: 00000000-0000-0000-0000-000000000000

storage

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

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/134.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2025-03-31T18:37:42.523Z

same,

you could build a workaround with a switch node and multiple wait nodes

Same here, I ended up going this route.

However this should be fixed

Still not fixed…

Still not fixed

Hi @lyfterteam

You can wrap it inside a sub-workflow, then use expressions as you like,

for example this:

      "parameters": {
        "resume": "timeInterval",
        "amount": 5,
        "unit": "seconds",
        "options": {}
      }

could be:

    {
      "parameters": {
        "resume": "{{ $json.Resume }}",
        "amount": {{ $json.seconds }},
        "unit": "seconds",
        "options": {}
      }

In other words, this is like a dynamic workflow that only contains the wait node.

Hey, thanks!

I already solved this in my workflow by using an If statement.

However, its still a bug that needs to be fixed