Node-RED exited with non-zero exit status 1

Hi, Node-RED team!

Node-Red keeps stopping at unspecified intervals. I suspect the email-node (node-red-node-email v 1.7.1); however, it works fine as long the process is running.

Here is the excerpt from the log file (redmatic.2019-11-07T05_41_21.948Z (1).log

Nov  7 01:31:10 ccu3-webui daemon.err node-red: 7 Nov 01:31:10 - [red] Uncaught Exception:
Nov  7 01:31:10 ccu3-webui daemon.err node-red: 7 Nov 01:31:10 - AssertionError [ERR_ASSERTION]: Input A expected to strictly equal input B:
Nov  7 01:31:10 ccu3-webui daemon.err node-red: + expected - actual ... Lines skipped
Nov  7 01:31:10 ccu3-webui daemon.err node-red: - ShutdownWrap {
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -   callback: [Function],
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -   handle: TLSWrap {
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -     [Symbol(owner)]: TLSSocket {
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -       [Symbol(asyncId)]: 7129973,
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -       [Symbol(connect-options)]: {
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -         checkServerIdentity: [Function: checkServerIdentity],
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -         ciphers: 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA256:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!SRP:!CAMELLIA',
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -         host: 'outlook.office365.com',
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -         minDHSize: 1024,
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -         rejectUnauthorized: false,
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -         singleUse: true,
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -         socket: Socket {
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -           [Symbol(asyncId)]: 7129978,
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -           [Symbol(kBytesRead)]: 0,
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -           [Symbol(kBytesWritten)]: 0,
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -           [Symbol(lastWriteQueueSize)]: 0,
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -           [Symbol(timeout)]: null,
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -           _events: [Object: null prototype] {
Nov  7 01:31:10 ccu3-webui daemon.err node-red: -             close: [
Nov  7 01:31:10 ccu3-webui daemon.err node-red: ...
Nov  7 01:31:10 ccu3-webui daemon.err node-red: + null
Nov  7 01:31:10 ccu3-webui daemon.err node-red: ...
Nov  7 01:31:10 ccu3-webui daemon.err node-red:     at JSStreamWrap.doWrite (internal/wrap_js_stream.js:151:12)
Nov  7 01:31:10 ccu3-webui daemon.err node-red:     at JSStream.onwrite (internal/wrap_js_stream.js:20:57)
Nov  7 01:31:10 ccu3-webui daemon.err node-red:     at Socket.ondata (internal/wrap_js_stream.js:64:22)
Nov  7 01:31:10 ccu3-webui daemon.err node-red:     at Socket.emit (events.js:198:13)
Nov  7 01:31:10 ccu3-webui daemon.err node-red:     at addChunk (_stream_readable.js:287:12)
Nov  7 01:31:10 ccu3-webui daemon.err node-red:     at readableAddChunk (_stream_readable.js:268:11)
Nov  7 01:31:10 ccu3-webui daemon.err node-red:     at Socket.Readable.push (_stream_readable.js:223:10)
Nov  7 01:31:10 ccu3-webui daemon.err node-red:     at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
Nov  7 01:31:10 ccu3-webui daemon.err node-red: Node-RED exited with non-zero exit status 1

Here also the flow in which the email-node is used: Email.Flow.txt

I'm using Node-RED version 1.0 (ported to Homematic as Redmatic 5.0.2

Please, tell me if you need any further information.
Thanks!

Start with the attached log excerpt and Email.Flow.txt, then inspect the email-node flow and the Node-RED 1.0 runtime context described in the report. Reproduce the intermittent shutdown if possible and determine the cause of the assertion; done means the reported flow no longer causes Node-RED to exit with status 1.