Describe the problem/error/question I tried to activate task runner via env var “N8N_RUNNERS_ENABLED=true”. But when this task runner is activated I have the following error in my code node that use puppeteer [image] For info, I update my Dockerfile to install puppeteer and the problems seems to …

I found a related topic but the problem seems to be solved with 1.83.0 but I use 1.83.2 and I still have the issue [image] Enabling Task Runners Breaks Workflows Questions Hello I recently enabled task runners on my self hosted instance and lots of my code nodes that use…

@netroy , Could you have a look please ? Seems the same than the issue fix by PR fix(core): Pass `NODE_PATH` to task runners by netroy · Pull Request #13652 · n8n-io/n8n · GitHub but for puppeteer I still have the issue

Can you please share a simple workflow to reproduce this issue? That would hopefully speed up the fix, if we can reproduce this. Please don’t summon people like this in posts. There is a long queue of unanswered questions here, and we are also busy with plenty of other tasks. Summoning people like …

Hello, Noted I won’t do it again. As you can see in WF just a require puppeteer trigger the error. For the installation of puppeteer I have the following conf in Dockerfile : RUN npm install -g npm@10.8.2 ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true ENV PUPPETEER_EXECUTAB…

I have a very similar problem when running puppeteer in a task runner, but in my case require(‘puppeteer’) works and the fail occurs on puppeteer.launch(). The code with complete scraping process works with task runners disabled. Bellow are some images with details about the code and error. [Capt…

It should be fixed in next version but you should add this env var yo make it work N8N_RUNNERS_ALLOW_PROTOTYPE_MUTATION=true

@Kent1 I’ve added the env and i’m currently on 1.89.2. I’ve successfully installed other packages like remeda but i’m getting the following with cctx. Do you think the next version will cover this? [image]

I tried, but still not working. Lets wait for the next version and see if this problem will be solved. My worry is ‘N8N_RUNNERS_ENABLED=true’ become default before this problem beeing solved.

This PR (not released in 1.89.2) fix the issue I could test it, and was a le to used puppeteer again. Just wait this PR be used in futur version fix(core): Propagate env to task runner (#14638) master ← propagate-env-to-task-run…

Task runner issue with external module

Questions

Kent1 March 20, 2025, 2:15pm 2

I found a related topic but the problem seems to be solved with 1.83.0 but I use 1.83.2 and I still have the issue

Topic		Replies	Views
External Task Runner v2.4.8: error when launching runner process Questions	3	858	February 4, 2026
Puppeteer in n8n V2 doesn't work anymore Questions	13	2295	January 19, 2026
Enabling Task Runners Breaks Workflows Questions	9	1358	March 12, 2025
Cannot import installed npm package in Code node (in task runner) Questions	4	167	March 18, 2026
PSA: v2.8.x - EXTERNAL TASK RUNNER BROKEN - NEED BETTER QA Questions core	3	240	March 9, 2026

Task runner issue with external module

Related topics