Debugging issue: This execution failed to be processed too many time

Questions
1

Hi, I have a bigger workflow for enriching leads.

And I always getting this error every 2-3h but I cannot find out why. My guess is because I am using google sheet and the google sheet API is limited? But why does it not say that G Sheet is the issue?

I am using custom server from elestio.

image
image1898×1324 103 KB

3

Hi @Luca2

Looking at your execution time of 1h 23m on such a large workflow, I’d also consider execution timeout or resource exhaustion on your Elestio server.

Can you share your EXECUTIONS_TIMEOUT setting, your Elestio server specs (RAM/CPU and which node the execution actually failed on?

4

That error is a queue worker timeout, not a Google Sheets thing. Your workflow runs for over an hour but the default lock duration is only 60 seconds so the worker thinks it stalled. Set QUEUE_WORKER_LOCK_DURATION=600000 in your env variables and it should stop happening.

5

It doenst say which node it fails on… that is the problem.

And so far I do not have any execution timeout.

6

@Luca2

For server specs on Elestio: Log into Elestio dashboard → select your service → look for RAM/CPU allocation in the service overview or settings page.

For Docker container logs: Elestio provides a logs section directly in the dashboard:

Go to your Elestio dashboard → select your n8n service → click “Logs” tab → look for any lines containing “killed”, “out of memory”, “OOM”, or “exit code 137”

Exit code 137 is the Linux signal for OOM kill, process was killed because the server ran out of memory.

For concurrency: look in your environment variables for N8N_CONCURRENCY_PRODUCTION_LIMIT.

Tell me what you found so we can actually move on with the troubleshooting !