Hi Guys, I have a workflow where I get clickup updates to control team tasks. The tasks are constantly updated, and the workflow is activated all the time, using the maximum of my cpu causing the machine to crash.
I’m using an instance in aws via docker, is it possible for me to make this workflow queue up, where it only activates again after a while? or is there another solution to my problem?
Please share the workflow
Information on your n8n setup
- n8n version:0.181.2
- Database you’re using (default: SQLite):SQLite
- Running n8n with the execution process [own(default), main]:own
- Running n8n via [Docker, npm, n8n.cloud, desktop app]:Docker
Welcome to the community @Vinicius_Pato!
The combination of a Trigger that triggers a lot and “own” mode is not great. Because you add a wait node directly afterward you even double the load as it has to create a new process, not just 1x, but actually 2x (1x when it gets triggered, then it is gets put to sleep again immediately, and then 1x once the 3-minute wait is over).
The simplest fix would be to switch to “main” mode.
Thanks @jan, looks like it solved my problem.
thank you again
You are welcome. That is great to hear!