I tried implementing it on my n8n cloud instance.
I then changed the “url”: “http://localhost:5678/rest/executions-current” to my url : “https://[hidden].app.n8n.cloud/rest/executions-current” but the flow is not valid (see below).
The answer from the http node doesn’t have the same info than with the local url - it’s a list of text. How is it possible to get the right info?
It doesn’t work in my case. Workflow execution is so fast that all instances see multiple executions in progress. My goal was to run the first iteration and ignore the following ones. But with this system, all iterations are ignored. It would be so much easier to prevent parallel execution at n8n level.
I added redis to my docker compose. It seems to work well as a workaround but this feature seems to be mandatory for real life cases (barcode scan for me).
You can change the first line in the Function-Node. Replace $workflow.id.toString() with the workflow you want to check for like for example '123'. Make sure that it is a string and not a number.
@jan ,
Just had a chance to run it on a server. The n8n instance is configured with basic auth but looks like the API requires n8n-auth cookie. is there a way around?
No misunderstanding at all buddy, The user management feature changed how the internal API works if you are using it or not. That being said I have not tried it without so it could be a similar process where you need to get the token to be able authenticate from the auth request.