Multiple executions stuck in 'running' status with Wait nodes on n8n Cloud

Questions
1

Describe the problem/error/question

I’m experiencing an issue with multiple workflow executions stuck in “running” status on my n8n Cloud instance for over 2 weeks. These executions appear to be stuck at Wait nodes and never resume.

Instance Details:

  • Instance URL: hivetechnologies.app.n8n.cloud
  • Workflow ID: qCSRPclJRPxOLThK
  • Workflow Name: “Dangerous Goods reviewer”

Stuck Execution IDs:

  • 11928 (since Oct 2, 2025)
  • 11932 (since Oct 2, 2025)
  • 11933 (since Oct 2, 2025)
  • 11934 (since Oct 2, 2025)
  • 11935 (since Oct 2, 2025)
  • 11939 (since Oct 2, 2025)
  • 11978 (since Oct 2, 2025)
  • 13441 (since Oct 9, 2025)

Symptoms:

  • All executions show status: "running" and finished: false
  • Timestamp inconsistencies: stoppedAt dates are before startedAt dates (e.g., stopped on Oct 2 but started on Oct 5)
  • Wait nodes configured for 3 days and 6 days are not resuming after the wait period
  • One execution (#12318) on Oct 3rd completed successfully, suggesting the issue started around Oct 2nd

Wait Nodes in Workflow:

  1. “Wait for Asana to be created” - 10 seconds
  2. “First follow up after 3 days” - 3 days
  3. “Escalation after 6 days” - 6 days

The workflow is currently in production for our dangerous goods approval process, so these stuck executions are blocking critical business operations.

What is the error message (if any)?

No error messages are displayed. The executions remain indefinitely in “running” status with finished: false.

Please share your workflow

(Cannot share full workflow due to business sensitivity, but the workflow structure includes a Webhook trigger → Processing nodes → Wait nodes (10 seconds, 3 days, 6 days) → Conditional logic → Notification nodes)

Share the output returned by the last node

N/A - The executions never reach completion. They get stuck at the Wait nodes.

Information on your n8n setup

n8n version: 1.108.1

Database (default: SQLite): n8n Cloud (managed database)

n8n EXECUTIONS_PROCESS setting (default: own, main): n8n Cloud default

Running n8n via (Docker, npm, n8n cloud, desktop app): n8n Cloud

Operating system: n8n Cloud

Additional Context

I found a similar issue in the community: Wait Node Is Not Releasing Executions where 860+ executions were stuck. The root cause was that “the primary box (not the workers) responsible
for adding delayed jobs to the queue wasn’t functioning.” The issue was resolved by restarting the primary server.

Could this be a similar infrastructure issue on n8n Cloud that requires a server restart?

2

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.