I am getting 503 errors on my workspace
In this article
In this article group
- How To Update To The Latest Stable Version In n8n Cloud
- n8n cloud trial FAQ
- How to Access and Install Verified Community Nodes in n8n Cloud
- How to add or modify execution limits on your Cloud Pro-2 monthly plan
- How to transfer ownership of your n8n instance to another e-mail
- Why didn’t I receive a Magic Link email?
- I have a feature request. Who do I talk to? How can I get this functionality added?
- How to Rename an n8n Cloud Instance
- How do I change my email?
- I want to cancel my paid subscription
- How do I delete my n8n account
- Can you reset my executions?
- How to download workflows from a backup
- 404 page and how to download your workflows when your instance is not available after an expired trial
- How Do I Change My n8n Cloud Plan
- Can I add or reset my n8n Assistant credits?
- How can I add more workflow executions?
- Can I use my own AI API key on n8n Cloud?
- Why do I have fewer n8n Assistant credits since 1 October 2026?
- Is n8n down?
Overview
If you're seeing a 503 error, it can have a few different causes, but the most common one is high memory usage in your workflows.
This occurs when an instance processes large amounts of data and exceeds the memory limits allocated to your current n8n Cloud plan. When this limit is reached, the instance may crash and become temporarily unavailable.
Why This Happens
Each n8n Cloud plan has a defined memory allocation. If your workflows:
Process large datasets
Handle multiple executions simultaneously
Store excessive data between nodes
Perform complex or resource-intensive operations
…they may exceed the available memory for your plan.
When this happens, the system may return a 503 error and stop responding until the instance restarts.
Memory Limits by Plan
You can view the memory allocations for each Cloud plan in our documentation:
Memory limits on each Cloud plan: Memory limits on each Cloud plan
How to Reduce Memory Consumption
To help prevent this issue, we recommend reviewing your workflows and applying memory optimisation best practices.
Our documentation provides detailed guidance here: How to reduce memory consumption in your workflow
Common optimisation strategies include:
Splitting large workflows into smaller ones via sub-workflows
Processing data in batches
Removing unnecessary data from workflow executions
Avoid pinning Large Binary Data
Avoid using the Code node where possible
Avoid manual executions when processing larger amounts of data
When to Consider Upgrading
If you’ve optimised your workflows and the error persists, you may need additional memory and CPU resources.
Upgrading to the next Cloud plan tier increases your available memory and overall performance capacity.
You can compare available plans here: n8n Pricing
Self-Hosted Option: Community Edition
For users who need more control over memory and CPU limits, the free self-hosted Community Edition allows you to configure your instance to meet your specific needs. As you can allocate resources according to the size and complexity of your workflows.
Learn more about self-hosting here: Self-hosting n8n
Need Further Help?
If you continue to experience issues after making adjustments, or if your instance doesn't recover on its own within several minutes, please contact our support team at help@n8n.io with:
The time the error occurred
The workflow(s) affected
Any recent changes made
Relevant logs or screenshots
We’ll be happy to help you review your setup.
Article Last Updated At: 2026-10-26T12:15:25.273Z