Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot read properties of undefined (reading 'id') #3014

Closed
thosanmaytinh opened this issue Mar 21, 2022 · 2 comments
Closed

Cannot read properties of undefined (reading 'id') #3014

thosanmaytinh opened this issue Mar 21, 2022 · 2 comments

Comments

@thosanmaytinh
Copy link

thosanmaytinh commented Mar 21, 2022

Describe the bug

/usr/local/lib/node_modules/n8n/dist/src/ResponseHelper.js:128
        id: fullExecutionData.id.toString(),
                              ^

TypeError: Cannot read properties of undefined (reading 'id')
    at Object.unflattenExecutionData (/usr/local/lib/node_modules/n8n/dist/src/ResponseHelper.js:128:31)
    at /usr/local/lib/node_modules/n8n/dist/src/WorkflowRunner.js:245:57
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

To Reproduce

My system has
1 n8n
1 webhook
2 workers
1 redis
1 postgres

Expected behavior
Ignore this error

@janober
Copy link
Member

janober commented Mar 21, 2022

Sorry but that information alone does not allow us to help you. You have to fill out the full issue template (right now you for example simply deleted the whole environment part). Additionally, do we also need a proper description on how to reproduce this. Right now all you did list is a rough overview on how your system looks like. That is comparable with a person coming to the hospital saying that he/she is human and they have stomach ache. It is for sure an important piece of the puzzle but this alone will not be enough to understand what is wrong with the patient. We for example do not even know which n8n version you are using, how your workflow looks like, if it happens always, only in production or manual testing, ...

Thanks!

@janober
Copy link
Member

janober commented Mar 27, 2022

As we did not receive any more information, do I now close this issue. You are obviously free to comment again any time with more data which will enable us to help you. We can then open this issue again if necessary.

We also merged recently #3032 which could help with this problem.

@janober janober closed this as completed Mar 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants