Workspace stuck in "In progress" / 503 error after Wait node execution

Questions
1

Describe the problem/error/question

<Hi community,
My n8n cloud workspace (sunlib.app.n8n.cloud) is completely stuck and returning 503 errors. I cannot access it at all.
What happened: I was testing a workflow that included a Wait node set to 120 seconds. After the workflow ran, the workspace became unresponsive and now shows “In progress” status permanently.
According to n8n support AI, this is likely caused by high memory consumption exceeding my plan’s limits.
Questions:
How can I get my workspace back online?
What is the maximum recommended Wait duration for n8n cloud?
Is there a better alternative to Wait nodes for long delays?
Thank you!!-- n8n Cloud users: If you’re experiencing issues with your cloud instance (e.g., can’t sign in, instance unavailable), please contact support at [email protected] →

What is the error message (if any)?

Please share your workflow

(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.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
1 Like
2

Hi @Julien_Bernard_SunLi, welcome to the n8n community :dizzy:
Please consider contacting the support in that case [email protected]
There’s no strict maximum Wait duration on n8n Cloud, but long blocking waits are not recommended; for longer delays, it’s better to use resume-based Wait or re-trigger the workflow via webhook or schedule instead of keeping the execution open.

3

Yeah this is a cloud infrastructure issue so you’ll need to email [email protected] (not support@) with your workspace URL and they can unstick it from their end. For future reference a 120s Wait should save state to the database but if the workflow was holding a lot of data in memory before the Wait that can still blow past your plan’s memory limit and crash things.