# Aggregation Error
**URL:** https://discourse.nodered.org/t/aggregation-error/100705
**Category:** General
**Created:** [2 April 2026 10:19 UTC](https://discourse.nodered.org/t/aggregation-error/100705 "2026-04-02T10:19:06Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@haegar33](https://discourse.nodered.org/u/haegar33)
#### Post date: [2 April 2026 10:19 UTC](https://discourse.nodered.org/t/aggregation-error/100705/1 "2026-04-02T10:19:06Z")
I got some strange behaviour and even short stalls of NR with a new MQTT Stream implemented for processing real time data from my car.
However before going into details about that I wonder whether the following reoccurring error message is related to MQTT or to another http request node?
```auto
Unhandled rejection RequestError: AggregateError
at new RequestError (/home/pi/.node-red/node_modules/request-promise-core/lib/errors.js:14:15)
at plumbing.callback (/home/pi/.node-red/node_modules/request-promise-core/lib/plumbing.js:87:29)
at Request.RP$callback [as _callback] (/home/pi/.node-red/node_modules/request-promise-core/lib/plumbing.js:46:31)
at self.callback (/home/pi/.node-red/node_modules/@cypress/request/request.js:183:22)
at Request.emit (node:events:508:28)
at Request.onRequestError (/home/pi/.node-red/node_modules/@cypress/request/request.js:869:8)
at ClientRequest.emit (node:events:508:28)
at emitErrorEvent (node:_http_client:107:11)
at TLSSocket.socketErrorListener (node:_http_client:574:5)
at TLSSocket.emit (node:events:508:28)
at emitErrorNT (node:internal/streams/destroy:170:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at processTicksAndRejections (node:internal/process/task_queues:90:21)
at runNextTicks (node:internal/process/task_queues:69:3)
at process.processTimers (node:internal/timers:540:9)
```
Any ideas?
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [2 April 2026 10:40 UTC](https://discourse.nodered.org/t/aggregation-error/100705/2 "2026-04-02T10:40:39Z")
If you go into your .node-red folder and run
`npm list request-promise-core`
what does it say?
Also show us the node red startup log please.
---
### Author:  [@haegar33](https://discourse.nodered.org/u/haegar33)
#### Post date: [2 April 2026 10:54 UTC](https://discourse.nodered.org/t/aggregation-error/100705/3 "2026-04-02T10:54:26Z")
npm list output:
```auto
node-red-project@0.0.1 /home/pi/.node-red
└─┬ node-red-contrib-telegrambot@16.4.0
└─┬ node-telegram-bot-api@0.66.0
└─┬ @cypress/request-promise@5.0.0
└── request-promise-core@1.1.3
```
Startup:
```auto
Welcome to Node-RED
===================
2 Apr 12:20:41 - [info] Node-RED version: v4.1.3
2 Apr 12:20:41 - [info] Node.js version: v24.11.0
2 Apr 12:20:41 - [info] Linux 6.12.48+deb13-amd64 x64 LE
2 Apr 12:20:42 - [info] Loading palette nodes
node-red-contrib-musiccast backend started.
2 Apr 12:20:57 - [info] node-red-contrib-telegrambot version: v16.4.0
2 Apr 12:21:04 - [info] Dashboard version 3.6.6 started at /ui
2 Apr 12:21:05 - [info] Settings file : /home/pi/.node-red/settings.js
2 Apr 12:21:05 - [info] HTTP Static : /home/pi/.node-red/myjs > /
2 Apr 12:21:05 - [info] Context store : 'default' [module=localfilesystem]
(node:272981) [DEP0190] DeprecationWarning: Passing args to a child process with shell option true can lead to security vulnerabilities, as the arguments are not escaped, only concatenated.
(Use `node --trace-deprecation ...` to show where the warning was created)
2 Apr 12:21:05 - [info] User directory : /home/pi/.node-red
2 Apr 12:21:05 - [warn] Projects disabled : editorTheme.projects.enabled=false
2 Apr 12:21:05 - [info] Flows file : /home/pi/.node-red/flows.json
2 Apr 12:21:05 - [info] Server now running at http://127.0.0.1:1880/
2 Apr 12:21:05 - [warn] Using unencrypted credentials
2 Apr 12:21:05 - [info] +-----------------------------------------------------
2 Apr 12:21:05 - [info] | 🌐 uibuilder v7.5.0 initialised
2 Apr 12:21:05 - [info] | root folder: /home/pi/.node-red/uibuilder
2 Apr 12:21:05 - [info] | Using Node-RED's webserver at:
2 Apr 12:21:05 - [info] | http://0.0.0.0:1880/
2 Apr 12:21:05 - [info] | Installed packages:
2 Apr 12:21:05 - [info] +-----------------------------------------------------
2 Apr 12:21:05 - [info] Starting flows
2 Apr 12:21:06 - [error] [tls-config:c5fcb747e8153ebe] Error: ENOENT: no such file or directory, open '/home/pi/nodedir/slicer_base64.cer'
2 Apr 12:21:06 - [info] [ui-base:UI-Name] Node-RED Dashboard 2.0 (v1.30.2) started at /dashboard
2 Apr 12:21:06 - [info] [ui-base:UI-Name] Created socket.io server bound to Node-RED port at path /dashboard/socket.io
2 Apr 12:21:07 - [info] [fritzbox-callmonitor:8d0aa669417fb6ba] Connecting to fritzbox...
2 Apr 12:21:07 - [info] Started flows
(node:272981) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 statusUpdate listeners added to [FritzboxConfig]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
...
...
```
Most of the startup errors are known. I see now its related to the Telegram node.....
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [2 April 2026 10:55 UTC](https://discourse.nodered.org/t/aggregation-error/100705/4 "2026-04-02T10:55:31Z")
> [@haegar33](#):
>
> `_http_client`
This node appears to be the culprit? Not MQTT I don't think. You should be able to search for it in your flows.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [2 April 2026 11:12 UTC](https://discourse.nodered.org/t/aggregation-error/100705/5 "2026-04-02T11:12:39Z")
> [@haegar33](#):
>
> `node-red-contrib-telegrambot`
I would start by upgrading to the latest version of the telegram node, and any other nodes. Also worth upgrading to the latest node-red.
It could potentially be a problem with the node with nodejs 24, it may not have had much testing with that version. Currently I think v22 is the recommended version with node-red.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [2 April 2026 11:14 UTC](https://discourse.nodered.org/t/aggregation-error/100705/6 "2026-04-02T11:14:33Z")
> [@Colin](#):
>
> nodejs 24
There certainly are some breaking changes in that version and beyond. But I think I did a quick check of the core of Node-RED and couldn't find any issues. 1 issue with UIBUILDER, fixed for the next release. So others might have issues but pretty rare.
---
### Author:  [@haegar33](https://discourse.nodered.org/u/haegar33)
#### Post date: [2 April 2026 13:54 UTC](https://discourse.nodered.org/t/aggregation-error/100705/7 "2026-04-02T13:54:45Z")
Looks like the most simple recipe is sometimes the best ..😉
Updating the Telegram node and NR to latest 4.1.8 was working. No further aggregation errors in the last hours.
Thanks!
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [16 April 2026 13:55 UTC](https://discourse.nodered.org/t/aggregation-error/100705/8 "2026-04-16T13:55:43Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.