Hi there, we’re running into a non-impactful issue where we get the following error when loading the Executions page to view previous executions:
ERROR RESPONSE TypeError: Cannot read property 'toString' of undefined at /usr/local/lib/node_modules/n8n/dist/src/Server.js:792:56 at async /usr/local/lib/node_modules/n8n/dist/src/ResponseHelper.js:70:26
We’ve been able to replicate the error doing the following:
- Create a “New Workflow” (but do not save it!)
- Add a node connected to the Start node
- Execute the workflow
- Check the Executions tab
It seems that if the Workflow hasn’t been saved, the database can’t relate any executed workflows to an existing workflow and throws the error.
Is there a way to force a user to save the workflow before it can be executed? Or give unsaved workflows the proper attributes so they show up under a different filter under Executions without the error?