🐛 [BUG] Evolution-Api 2.3.6 Not Working Send-Text not working on some phone numbers

[YzKencebay]

Welcome!

• Yes, I have searched for similar issues on GitHub and found none.

What did you do?

Hello, I am using Evolution-Api 2.3.6 but Send-Text is not working on some numbers and it says "waiting for message" and it may take some time. However, on some numbers it does not give this error and sends the message directly. I am open to your suggestions for solutions.

What did you expect?

I think working.

What did you observe instead of what you expected?

While sending messages to some numbers, I encountered the problem of waiting for a WhatsApp message, which may take some time. Some numbers did not have this error and sent the message directly.

Screenshots/Videos

No response

Which version of the API are you using?

Evolution-Api 2.3.6

What is your environment?

Docker

Other environment specifications

Windows Server 2022 4cpus 16gb ram

If applicable, paste the log output

No response

Additional Notes

No response

[TrolljanO]

@YzKencebay Can you send your stack logs and configs?

[YzKencebay]

@YzKencebay Can you send your stack logs and configs?

2025-11-28 17:37:02 [Evolution API] v2.3.6 177 - Fri Nov 28 2025 11:37:02 ERROR [WebhookController] [object]
2025-11-28 17:37:02 {
2025-11-28 17:37:02 local: 'p.sendData-Webhook',
2025-11-28 17:37:02 message: 'Erro não recuperável (404): Request failed with status code 404. Cancelando retentativas.',
2025-11-28 17:37:02 statusCode: 404,
2025-11-28 17:37:02 url: 'http://host.docker.internal:5678/webhook/evolution_test',
2025-11-28 17:37:02 server_url: 'http://localhost:9091'
2025-11-28 17:37:02 }
2025-11-28 17:37:02
2025-11-28 17:37:02 [Evolution API] v2.3.6 177 - Fri Nov 28 2025 11:37:02 ERROR [WebhookController] [object]
2025-11-28 17:37:02 {
2025-11-28 17:37:02 local: 'p.sendData-Webhook',
2025-11-28 17:37:02 message: 'Todas as tentativas falharam: Request failed with status code 404',
2025-11-28 17:37:02 hostName: undefined,
2025-11-28 17:37:02 syscall: undefined,
2025-11-28 17:37:02 code: 'ERR_BAD_REQUEST',
2025-11-28 17:37:02 error: undefined,
2025-11-28 17:37:02 stack: 'AxiosError: Request failed with status code 404\n' +
2025-11-28 17:37:02 ' at settle (/evolution/node_modules/axios/dist/node/axios.cjs:2097:12)\n' +
2025-11-28 17:37:02 ' at IncomingMessage.handleStreamEnd (/evolution/node_modules/axios/dist/node/axios.cjs:3305:11)\n' +
2025-11-28 17:37:02 ' at IncomingMessage.emit (node:events:520:35)\n' +
2025-11-28 17:37:02 ' at endReadableNT (node:internal/streams/readable:1701:12)\n' +
2025-11-28 17:37:02 ' at process.processTicksAndRejections (node:internal/process/task_queues:90:21)\n' +
2025-11-28 17:37:02 ' at Axios.request (/evolution/node_modules/axios/dist/node/axios.cjs:4483:41)\n' +
2025-11-28 17:37:02 ' at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n' +
2025-11-28 17:37:02 ' at async Io.retryWebhookRequest (/evolution/dist/main.js:315:65415)\n' +
2025-11-28 17:37:02 ' at async Io.emit (/evolution/dist/main.js:315:64226)\n' +
2025-11-28 17:37:02 ' at async Mo.emit (/evolution/dist/main.js:315:70097)\n' +
2025-11-28 17:37:02 ' at async eo.sendDataWebhook (/evolution/dist/main.js:173:17316)',
2025-11-28 17:37:02 name: 'AxiosError',
2025-11-28 17:37:02 url: 'http://host.docker.internal:5678/webhook/evolution_test',
2025-11-28 17:37:02 server_url: 'http://localhost:9091'
2025-11-28 17:37:02 }
2025-11-28 17:37:02

[TrolljanO]

@YzKencebay Its important give more details to trace the bug.

Please share you config too...

Is it build on docker-compose?

[YzKencebay]

@YzKencebay Its important give more details to trace the bug.

Please share you config too...

Is it build on docker-compose?

services:
api:
container_name: evolution_api_236
image: evoapicloud/evolution-api:latest
restart: always
depends_on:
- redis
- evolution-postgres
ports:
- "9091:9091"
volumes:
- evolution_instances_236:/evolution/instances
networks:
- evolution-net
- dokploy-network
env_file:
- .env236
expose:
- "9091"

redis:
container_name: evolution_redis_236
image: redis:latest
restart: always
command: >
redis-server --port 6379 --appendonly yes
volumes:
- evolution_redis_236:/data
networks:
evolution-net:
aliases:
- evolution-redis-236
dokploy-network:
aliases:
- evolution-redis-236
expose:
- "6379"

evolution-postgres:
container_name: evolution_postgres_236
image: postgres:15
restart: always
env_file:
- .env236
command:
- postgres
- -c
- max_connections=1000
- -c
- listen_addresses=*
environment:
- POSTGRES_DB=evolution_db_236
- POSTGRES_USER=xxx
- POSTGRES_PASSWORD=xxxxxxxxxx
volumes:
- postgres_data_236:/var/lib/postgresql/data
ports:
- "5444:5432"
networks:
- evolution-net
- dokploy-network
expose:
- "5432"

volumes:
evolution_instances_236:
evolution_redis_236:
postgres_data_236:

networks:
evolution-net:
name: evolution-net
driver: bridge
dokploy-network:
external: true

[YzKencebay]

O meu deu erro também, mas resolvi dessa forma:

Em algumas versões da BAILEYS / Evolution API , quando o contato usa WhatsApp Business, o remoteJid pode vir com o sufixo diferente:

@lid

Ou vir vazio/indefinido, dependendo da origem

Nesses casos, a API fornece remoteJidAlt como o JID alternativo, que geralmente é o JID normalizado, por exemplo:

5511999999999@s.whatsapp.net

Resolvi assim:

Sua expressão resolve isso perfeitamente

{{ ( $json.body.data.key.remoteJid.endsWith('@lid') ? $json.body.data.key.remoteJidAlt : $json.body.data.key.remoteJid ) .toString() .replace(/[\n\r\t ]+/g, '') }}

O que ela faz?

Se o JID terminar com @lid → usa remoteJidAlt Isso corrige o formato quando vem de contas Business ou Multi-Device.

Senão → usa o próprio remoteJid Isso cobre WhatsApp normal.

.replace(/[\n\r\t ]+/g, '') Remove quebras de linha, tabs e espaços.

///////////////////////////////// ENGLISH

Mine gave an error too, but I solved it this way:

In some versions of BAILEYS / Evolution API, when the contact uses WhatsApp Business, the remoteJid may come with a different suffix:

@lid

Or it may come empty/undefined depending on the source.

In these cases, the API provides remoteJidAlt as the alternative JID, which is usually the normalized JID, for example:

5511999999999@s.whatsapp.net

I solved it like this:

Your expression handles this perfectly:

{{ ( $json.body.data.key.remoteJid.endsWith('@lid') ? $json.body.data.key.remoteJidAlt : $json.body.data.key.remoteJid ) .toString() .replace(/[\n\r\t ]+/g, '') }}

What does it do?

If the JID ends with @lid → it uses remoteJidAlt This fixes the format when it comes from Business or Multi-Device accounts.

Otherwise → it uses remoteJid This covers regular WhatsApp accounts.

.replace(/[\n\r\t ]+/g, '') Removes line breaks, tabs, and any extra spaces.

I will try

[TrolljanO]

@YzKencebay

2025-11-28 17:37:02 name: 'AxiosError',
2025-11-28 17:37:02 url: 'http://host.docker.internal:5678/webhook/evolution_test',
2025-11-28 17:37:02 server_url: 'http://localhost:9091/'
2025-11-28 17:37:02 }
2025-11-28 17:37:02

reading these lines, I think you need to set up correctly your webhook URL.
If It was buily on Docker-Compose, you need to make sure the containers share the same network.
And you need to reference the service name in URI.

e.g.:
❌ :

 url: 'http://host.docker.internal:5678/webhook/evolution_test'

✔️ :

url: 'http://n8n:5678/webhook/evolution_test'

Check your .env file.
Try disabling the global webhook if you are not using it.

[YzKencebay]

@YzKencebay

2025-11-28 17:37:02 name: 'AxiosError',
2025-11-28 17:37:02 url: 'http://host.docker.internal:5678/webhook/evolution_test',
2025-11-28 17:37:02 server_url: 'http://localhost:9091/'
2025-11-28 17:37:02 }
2025-11-28 17:37:02

reading these lines, I think you need to set up correctly your webhook URL. If It was buily on Docker-Compose, you need to make sure the containers share the same network. And you need to reference the service name in URI.

e.g.: ❌ :

 url: 'http://host.docker.internal:5678/webhook/evolution_test'

✔️ :

url: 'http://n8n:5678/webhook/evolution_test'

Check your .env file. Try disabling the global webhook if you are not using it.

I will Try thank you

[YzKencebay]

O meu deu erro também, mas resolvi dessa forma:

Em algumas versões da BAILEYS / Evolution API , quando o contato usa WhatsApp Business, o remoteJid pode vir com o sufixo diferente:
@lid
Ou vir vazio/indefinido, dependendo da origem
Nesses casos, a API fornece remoteJidAlt como o JID alternativo, que geralmente é o JID normalizado, por exemplo:
5511999999999@s.whatsapp.net

Resolvi assim:

Sua expressão resolve isso perfeitamente
{{ ( $json.body.data.key.remoteJid.endsWith('@lid') ? $json.body.data.key.remoteJidAlt : $json.body.data.key.remoteJid ) .toString() .replace(/[\n\r\t ]+/g, '') }}

O que ela faz?

Se o JID terminar com @lid → usa remoteJidAlt Isso corrige o formato quando vem de contas Business ou Multi-Device.
Senão → usa o próprio remoteJid Isso cobre WhatsApp normal.
.replace(/[\n\r\t ]+/g, '') Remove quebras de linha, tabs e espaços.
///////////////////////////////// ENGLISH
Mine gave an error too, but I solved it this way:
In some versions of BAILEYS / Evolution API, when the contact uses WhatsApp Business, the remoteJid may come with a different suffix:
@lid
Or it may come empty/undefined depending on the source.
In these cases, the API provides remoteJidAlt as the alternative JID, which is usually the normalized JID, for example:
5511999999999@s.whatsapp.net

I solved it like this:

Your expression handles this perfectly:
{{ ( $json.body.data.key.remoteJid.endsWith('@lid') ? $json.body.data.key.remoteJidAlt : $json.body.data.key.remoteJid ) .toString() .replace(/[\n\r\t ]+/g, '') }}

What does it do?

If the JID ends with @lid → it uses remoteJidAlt This fixes the format when it comes from Business or Multi-Device accounts.
Otherwise → it uses remoteJid This covers regular WhatsApp accounts.
.replace(/[\n\r\t ]+/g, '') Removes line breaks, tabs, and any extra spaces.

I will try
Thanks for the information, I solved the problem. When the number was closed, I activated the webhook and sent a message.

[YzKencebay]

@YzKencebay

2025-11-28 17:37:02 name: 'AxiosError',
2025-11-28 17:37:02 url: 'http://host.docker.internal:5678/webhook/evolution_test',
2025-11-28 17:37:02 server_url: 'http://localhost:9091/'
2025-11-28 17:37:02 }
2025-11-28 17:37:02

reading these lines, I think you need to set up correctly your webhook URL. If It was buily on Docker-Compose, you need to make sure the containers share the same network. And you need to reference the service name in URI.
e.g.: ❌ :

 url: 'http://host.docker.internal:5678/webhook/evolution_test'

✔️ :

url: 'http://n8n:5678/webhook/evolution_test'

Check your .env file. Try disabling the global webhook if you are not using it.

I will Try thank you

Thanks for the information, I solved the problem. When the number was closed, I activated the webhook and sent a message.

[CesareIsHere]

Hello everyone,
I'm experiencing the same issue with the same configuration, but I don't have any webhooks configured. Currently, this problem is affecting only one instance.
Could someone help me troubleshoot this? I also didn't fully understand the proposed solution—specifically, what does "number was closed" mean in this context?
Any assistance would be greatly appreciated. Thank you!

[YzKencebay]

Hello everyone, I'm experiencing the same issue with the same configuration, but I don't have any webhooks configured. Currently, this problem is affecting only one instance. Could someone help me troubleshoot this? I also didn't fully understand the proposed solution—specifically, what does "number was closed" mean in this context? Any assistance would be greatly appreciated. Thank you!

"Hello, first I received a message via the webhook from the relevant number and sent a message that way. Later, after disconnecting the webhook, I was able to send messages without using the webhook. This is how I solved the issue."