Something wrong about version 0.140.0?

Questions
1

Screenshot (3)
Screenshot (3)462×562 19.5 KB

A lot of Unkown status.

and running always,It can not stop.

  • today at 2:46:38 PM (node:21) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ‘data’ of undefined
  • today at 2:46:38 PM at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/NodeExecuteFunctions.js:252:42
  • today at 2:46:38 PM at processTicksAndRejections (internal/process/task_queues.js:93:5)
  • today at 2:46:38 PM (Use node --trace-warnings ... to show where the warning was created)
  • today at 2:46:38 PM (node:21) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see Command-line API | Node.js v17.8.0 Documentation). (rejection id: 2)
  • today at 2:46:38 PM (node:21) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  • today at 2:48:38 PM (node:47) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ‘data’ of undefined
  • today at 2:48:38 PM at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/NodeExecuteFunctions.js:252:42
  • today at 2:48:38 PM at processTicksAndRejections (internal/process/task_queues.js:93:5)
  • today at 2:48:38 PM (Use node --trace-warnings ... to show where the warning was created)
  • today at 2:48:38 PM (node:47) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see Command-line API | Node.js v17.8.0 Documentation). (rejection id: 2)
  • today at 2:48:38 PM (node:47) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I just use the HTTPREQUEST to get Movie Magnet Bot feed Movie Magnet Bot feed content.

some logs:

  • today at 5:10:54 PM (node:2522) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ‘data’ of undefined
  • today at 5:10:54 PM at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/NodeExecuteFunctions.js:252:42
  • today at 5:10:54 PM at processTicksAndRejections (internal/process/task_queues.js:93:5)
  • today at 5:10:54 PM (Use node --trace-warnings ... to show where the warning was created)
  • today at 5:10:54 PM (node:2522) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see Command-line API | Node.js v17.8.0 Documentation). (rejection id: 2)
  • today at 5:10:54 PM (node:2522) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
2

Hey @aston_he,

Thank you for reporting the issue. We are looking into it.

3

Sorry to hear about the issues @aston_he

I implemented a fix for this here: Improve errors returned by Axios to improve compatbility by krynble · Pull Request #2262 · n8n-io/n8n · GitHub

We will be releasing a hotfix for this soon.

4

Fix got released with [email protected]

5

I get some error after update to the newest version.
But it worked well in the previous version.
I do not know why.

Screenshot (4)

6

Can you please share those errors.

7

Just these in logs:

  • today at 1:40:48 PM Failed saving execution progress to database for execution ID 23191 (hookFunctionsPreExecute, nodeExecuteAfter)
  • today at 1:40:49 PM Failed saving execution progress to database for execution ID 23191 (hookFunctionsPreExecute, nodeExecuteAfter)
  • today at 1:41:01 PM Failed saving execution progress to database for execution ID 23190 (hookFunctionsPreExecute, nodeExecuteAfter)
  • today at 6:10:48 PM Failed saving execution progress to database for execution ID 23541 (hookFunctionsPreExecute, nodeExecuteAfter)
8

What database are you using and what mode are you running n8n (main, own)?

9

I use the default database.
mode:own

10

I assume you have the option “Save Execution Progress” activated for that workflow. In this case, it is best to change the mode to “main” or use another database.

The reason is that SQLite locks the database and if multiple processes access it at the same time problems will occur very fast. If you use “main” mode that would not happen (as there is only one process) also if you use another database as they do not have the same problem as SQLite.

11

But this can not happen in version 0.138.0.

12

Then sadly do not have an explanation for that right now. But the above issue that it can not save after every node with multiple executions in parallel did always exist and will always exist with “own” mode and SQLite.

And does it also work with 0.139.1?

13

It does not work in 0.139.1 .