You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have managed to reproduce this on 1.75.1 which would suggest the 2 commits you have found could be unrelated as neither of them are in that version. Are you sure you are looking at the correct commit versions?
Commits aside... This is with the team to be looked into.
I think I have worked out what the problem could be, I am just waiting for my local instance to update but we recently a few hours ago set N8N_RUNNERS_ENABLED to true as the default option which has been set on my personal instance for a while.
If you set N8N_RUNNERS_ENABLED to false it should start working on the latest version.
Thank you for bringing this into our attention! The reason why are seeing this is like @Joffcom explained. We enabled Task Runners by default recently. Task Runner has better performance and is more secure compared to the old way of execution Code node code. Unfortunately certain JS libraries are not compatible with the runtime hardening we are doing. We are looking into this and figuring how we can still keep supporting libraries like cron-parser with Task Runner.
Bug Description
Get the error
Cannot assign to read only property 'toString' of object '#<CronDate>'
because of this line:const cronParser = require('cron-parser')
This worked fine in commit ac2f647. But broke when updating to 565c7b8.
To Reproduce
The workflow below reproduces the error. I did add the environment-variable
NODE_FUNCTION_ALLOW_EXTERNAL=cheerio,cron-parser
in my Render-environment.Expected behavior
Give no error when I run
const cronParser = require('cron-parser')
Operating System
Render webservice
n8n Version
1.75.0
Node.js Version
22.10.0
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: