Force Save before Execution

Questions
1

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:

  1. Create a “New Workflow” (but do not save it!)
  2. Add a node connected to the Start node
  3. Execute the workflow
  4. 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?

Thanks!

2

I am also running into this same issue - is there any work being done on this?

Thanks!
Dakota

3

Really sorry @Ian_Taggart that issues must have slipped through.

Welcome to the community @dakotaheyman!

Did some testing. It seems like that only happens if

EXECUTIONS_DATA_SAVE_MANUAL_EXECUTIONS=true

That probably explains why not to many people got that error. Anyway is now fixed and will be released with the next version.

4

No worries @jan, thank you for your continued effort on improving n8n! Appreciate all of your help.

5

Thanks a lot for understanding! But in the future it is really totally OK to simply comment on an issue again and mention me to bring it to the top.

6

Wow that was fast :slight_smile: , thanks @jan !