High CPU Usage and Constant HTTP 200 Errors to N8N Webhook - Started Yesterday

[DevNeuronex]

Bug Description

I'm experiencing severe performance issues with Evolution API v2.2.3 that started suddenly on August 19th, 2025. The main problems are:
High CPU Usage: Server CPU utilization spiked dramatically for no apparent reason
Constant HTTP 200 webhook calls: Getting continuous connection.update events sent to N8N webhook endpoint with "connecting" state
Performance degradation: Issue became worse when upgrading to v2.3.1, so rolled back to v2.2.3
Based on the logs, the instance "laboratoriosaolucas" is stuck in a constant connecting loop, sending webhook notifications every few seconds to N8N.

To Reproduce

To Reproduce

Set up Evolution API v2.2.3 with N8N webhook integration
Configure instance with webhook URL pointing to N8N
Instance gets stuck in "connecting" state (statusReason: 200)
Observe continuous webhook calls to N8N endpoint
Monitor server CPU usage spike

Expected behavior

Expected behavior

Instance should connect successfully without getting stuck in connecting state
Webhook should only send connection updates when state actually changes
CPU usage should remain stable
No infinite loop of connection attempts

Debug Info

Debug Info
Configuration:
yamlenvironment:

• CONFIG_SESSION_PHONE_VERSION=2.3000.1023204200
• CACHE_REDIS_ENABLED=true
• CACHE_REDIS_URI=redis://redis:6379/6
• CACHE_REDIS_SAVE_INSTANCES=false
• CACHE_LOCAL_ENABLED=false

N8N Webhook Log Sample:
[
{
"headers": {
"host": "n8n.neuronex.tec.br",
"user-agent": "axios/1.7.9",
"content-length": "376",
"accept-encoding": "gzip, compress, deflate, br",
"content-type": "application/json",
"x-forwarded-for": "44.205.120.57",
"x-forwarded-host": "n8n.neuronex.tec.br",
"x-forwarded-port": "443",
"x-forwarded-proto": "https",
"x-forwarded-server": "624e59235de9",
"x-real-ip": "44.205.120.57"
},
"params": {},
"query": {},
"body": {
"event": "connection.update",
"instance": "laboratoriosaolucas",
"data": {
"instance": "laboratoriosaolucas",
"state": "connecting",
"statusReason": 200
},
"destination": "https://n8n.neuronex.tec.br/webhook-test/labsaolucas",
"date_time": "2025-08-20T14:59:30.777Z",
"sender": "5519989070725@s.whatsapp.net",
"server_url": "http://localhost:8080",
"apikey": "xxx-yyy-zzz-xxx"
},
"webhookUrl": "https://n8n.neuronex.tec.br/webhook-test/labsaolucas",
"executionMode": "test"
}
]

Operating System

Ubuntu 24.04.2 LTS (AWS EC2)

n8n Version

Latest (receiving webhooks from Evolution API)

Node.js Version

18 (Alpine - running in Docker)

Database

PostgreSQL

Execution mode

queue

Hosting

self hosted

[Joffcom]

Hey @DevNeuronex,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-3917".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

[Joffcom]

Hey @DevNeuronex,

Is this an issue with n8n or Evolution? It sounds like Evolution is spamming the n8n instance with connections.

[DevNeuronex]

Probably it’s the Evolution API, because I haven’t seen anybody complain about that. Even baileys lib

[DiegoAugustusCunha]

What solved this problem on our servers was a preventative measure to limit CPU usage per container, preventing them from increasing processing to the point of collapse.

We believe this is due to multiple browsers being opened with each instance created, and over time this causes the problem to collapse.

The command we used was: docker update --cpus=0.4 /*NumContainer*/

[krisn0x]

Sounds like this is on the Evolution API, so I will close this. Feel free to reopen if incorrect or you want us to take another look for any reason. Thank you!