It could be that you are using multiple commands (using && to string them together). The CLI execution environment (i.e. nodejs emulated shell environment) might not support that, but it should support running a single script (.bat, .cmd) that strings all of those individual commands together for you. Have you tried that?
@smalldude I would recommend using dockers with n8n, people have strange issues when using npm with env vars etc, but using && should work, but it seems the last command is
&& {{ $json.videoid }}
Which seems maybe just hanging, what the actual value of && {{ $json.videoid }} in the flow?
Have you tried running this just in a normal terminal?
I would test with just cd, soo what location it’s all being executed in, to see if the CD into folder is going right place. Also because the py runs in the middle, it could be erroring but not catching because of the last command.
Maybe try seperate execute command nodes to isolate issues should help fix it.
Most of the solutions that you have mentioned trying I have already tried, except running the instance in docker.
I also can’t separate the command into different execute nodes because the cd command isn’t saved across nodes so I would have to rerun it in each node. This I have also tried and still doesn’t work.
@King_Samuel_David I reinstalled n8n in docker (finally) but the execute command node still runs indefinitely. Is there anything else that I haven’t tried? Also to answer your question, the "{videoid} field is just a string for the video id for a youtube video. Essentially the execute command node runs a python script located in the container that asks for input (The videoid) and spits out the transcript for that youtube video.
