@Valentin Ffrench Hi Valentin. Thanks for your response. I was able to reproduce the error in a very simple workflow. used a simple “trigger workflow” (Scheduled Trigger) and the main workflow with the new Think node. When I execute the workflows manually, everything works perfectly, even in the context with the Think node. However, as soon as I switch the workflows to “active”, the errors are always generated. Note: I already had a similar problem related to Postgres nodes after an N8N version upgrade. In the end, the solution was to downgrade the version of the Postgres node (from 2.6 to 2.5).

Thanks @Norbert Walczak ! Looks like the problem is solved. How do you handle the creation of new workflows with Postgres? By copying existing nodes of version 2.4?

@Norbert Walczak 🙏 THANK YOU!