Facing this issue all the time today. And I don’t restart the workspace.
I can ender the workspace for couple of minutes and then again
Does anybody know what can it be?
Your workspace is restarting and currently offline. If you continue to see this page, contact support.
Are you a workspace owner? Open Admin Panel
Welcome to the n8n community @AndrAnt !
What I’d check first is the Admin Panel for any signs of repeated restarts or resource issues. I’d also think about whether anything changed today, like enabling a heavy workflow, AI nodes, or something that could spike memory/CPU. If nothing obvious changed, I’d treat this as a platform issue and reach out to n8n Cloud support, since persistent 503 errors like this aren’t expected under normal conditions.
Hi @AndrAnt Welcome!
If this issue persists for a long time, consider reaching out to support, as they can inspect your workspace closely and resolve your issue.
Yes, I see “Execution stopped at this node
n8n may have run out of memory while running this execution…” What can I do with this?
Look’s like found the issue: I’m working with txt files: adding text from file B at the end of file A. Ectualy doing it by downloading text from file A then upend it with file B and insert it back to file A. The file A is now more then 7 MB and the flow crushs wit “n8n may have run out of memory while running this execution“. Do you know what the limitations are or may be how can I avoide the issue?
If I download file A, append file B in the workflow, and then write the full result back, n8n has to keep that data in memory during execution. On Cloud, memory-heavy workflows can crash the instance and make the workspace go offline.
So I wouldn’t treat this as a webhook or workspace bug first. I’d treat it as an out-of-memory issue caused by rebuilding the whole file inside the workflow.
What I’d try next is avoiding the full read-modify-write pattern. If your storage supports append, I’d use that directly. Otherwise, I’d switch to chunking or move the merge step outside n8n.