Hello.
Queue mode is the way how n8n can scale - by adding more worker and webhook instances. However it is also known that manually executed workflows are executed by main instance.
Now let’s assume that we have a large number of users simultaneously working with the n8n interface and running long tasks manually. Do I understand correctly that in this case all executions will be processed by the only one main n8n instance? If so, then how this work scenario can be scaled?
Do I understand correctly that in this case all executions will be processed by the only one main n8n instance?
You’re quite right here.
If so, then how this work scenario can be scaled?
I think one possible option would be to add a webhook node as an additional trigger. Then activate your workflow and call the webhook production URL as often as needed. You can do this in your browser if needed, meaning you’d still be manually triggering an execution, but n8n would treat it as a production execution.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.