Some workflows failing to execute since upgrading to 0.199.0

Questions
#1

Describe the issue/error/question

Since upgrading to 0.199.0, some of my scheduled workflows are failing with the following error:

"Cannot read properties of undefined (reading 'nodeExecutionStack')"

The workflow runs fine if I run it manually.

Please share the workflow

Withheld for security reasons (almost every node requires me to sanitize the data before posting here)

Share the output returned by the last node

The workflow doesn’t run so none of the nodes output data. If I run it manually it works fine and all nodes have the green checkmark

Information on your n8n setup

  • n8n version: 0.199.0
  • Database you’re using (default: SQLite): Postgres
  • Running n8n with the execution process [own(default), main]: own
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: K8s
#2

Do those workflows then always fail or only sometimes? If it is the former can you please share a workflow that allows us to reproduce the problem, because else it is probably hard to find what is going wrong here.

#3

This is odd but it seems like they’re working now.

Actually when I dug deeper there was another error indicating they were unable to access the records in the database (The first error was very generic as you can see).

Also it seems like when this happens, it always fails the manual rerun no matter what (though subsequent scheduled runs and “from scratch” manual runs work).

So I think this is a problem with my database connection limits not with the new version (it just happened to be right after I upgraded and was happening on multiple workflows, and because the schedueld reruns were failing I thought it was a deeper rooted issue).

My apologies for thinking it was due to upgrade.

Thanks Jan,

#4

Just adding to this in case anyone else comes across this issue.

I’ve done a couple of things which seems to have helped:

  • Configured a connection pool for Postgres
  • Configured scaling for n8n

Adding a worker node especially has helped for large workflows with lots of nodes in them.

Def worth pursuing if you plan to self-host and utilize the true power of n8n :fire: