Our n8n Cloud is behaving weird recently. The execution is slow first of all. And it is not completing the execution fully and completing in the mid way. While checking it on executions it says error at some time stamp. But actually there is no error. I have attached a screenshot below,
1 Like
Hi @Victor_Mondal
this looks like a Out of Memory crash or a worker timeout on the n8n cloud infrastructure. the worker is likely dying before it can even report the error.
here’s what to try:
- restart the cloud instance: this clears out any stuck processes and should fix the slowness.
- optimize the workflow:
- check batch sizes: if you’re pushing >50MB of data or >1,000 items at once, you need to use the Split In Batches node so it doesn’t max out the RAM.
- check code nodes: if you’re doing heavy data mapping, make sure no single script takes longer than 60 seconds to run, or the cloud orchestrator will kill it.
- check database bloat: if your “Executions” tab is struggling to load, your execution history is probably too large.
hope this will help you!
1 Like
Hi @Victor_Mondal
Are these executions hitting your plan’s maximum runtime limit? Some of them are running for nearly an hour or more, which makes me think they might be getting terminated rather than failing due to a node error. Are you calling external APIs that could be hanging or taking too long to respond?
This looks like you’re hitting the execution timeout limit on cloud, those runs are going for almost an hour which is wild. Check what plan you’re on because there’s definitely a max runtime and once it hits that it just kills the execution without a proper error message. If you’ve got long-running API calls or big data batches that’s probably your culprit, might need to break things up with Split In Batches or optimize whatever’s taking so long.