8 Feb 21:24:04 - [info] Installed module: node-red-contrib-ctrlx-automation 8 Feb 21:24:04 - [info] Added node types: 8 Feb 21:24:04 - [info] - node-red-contrib-ctrlx-automation:ctrlx-config 8 Feb 21:24:04 - [info] - node-red-contrib-ctrlx-automation:ctrlx-datalayer-request (node:5412) UnhandledPromiseRejectionWarning: CtrlxProblemError: [401] Unauthorized at Function.fromHttpResponse (C:\Users\rim5cer\.node-red\node_modules\node-red-contrib-ctrlx-automation\lib\CtrlxProblemError.js:115:31) at ClientRequest. (C:\Users\rim5cer\.node-red\node_modules\node-red-contrib-ctrlx-automation\lib\CtrlxCore.js:245:36) at Object.onceWrapper (events.js:422:26) at ClientRequest.emit (events.js:315:20) at HTTPParser.parserOnIncomingClient (_http_client.js:641:27) at HTTPParser.parserOnHeadersComplete (_http_common.js:126:17) at TLSSocket.socketOnData (_http_client.js:509:22) at TLSSocket.emit (events.js:315:20) at addChunk (internal/streams/readable.js:309:12) at readableAddChunk (internal/streams/readable.js:284:9) (Use `node --trace-warnings ...` to show where the warning was created) (node:5412) 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 https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:5412) [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. 8 Feb 21:25:43 - [info] Stopping flows 8 Feb 21:25:43 - [info] Stopped flows 8 Feb 21:25:43 - [info] Starting flows 8 Feb 21:25:43 - [info] Started flows 8 Feb 21:25:52 - [info] Stopping flows