[Bug] Unable to send messages (ACK 463) after WhatsApp Business reinstall - instance OPEN, receiving works normally

Start by reproducing an outgoing send through the Evolution Manager and inspect the logged ACK 463 response, status change, addressingMode, and @lid recipient resolution. Compare behavior with the reported Baileys and Evolution API versions; done means outgoing messages are delivered after reinstalling and reconnecting an instance.

Environment

• Evolution API: v2.3.7
• Image: evoapicloud/evolution-api:v2.3.7
• Deployment: EasyPanel (official template)
• WhatsApp Library: Baileys
• Database: PostgreSQL
• Redis: Enabled
• Operating System: Ubuntu (VPS)

---

Problem

The Evolution instance connects successfully and remains OPEN.

Incoming messages are received normally.

However, every outgoing message fails.

The Evolution Manager accepts the send request, but the message changes from status 1 to 0, and the recipient never receives it.

---

Logs

Every send attempt produces:

text
Sending message to XXXXX@s.whatsapp.net
sending message to 5 devices
received error in ack
error: "463"
status: 0
messageStubParameters: ["463"]

The logs also show:
addressingMode: "lid"

and recipients are resolved as:
xxxxxxxxxxxxx@lid

What happened before the problem

The issue started approximately 3 days ago.

Before that:

• WhatsApp Business was reinstalled.
• No chat backup was restored.
• A completely new Evolution instance was created after the reinstall.
• The instance was connected again using a new QR Code.

So this is not an old session.

• What has already been tested
• Recreated the instance.
• Connected using a new QR Code.
• PostgreSQL verified.
• Redis verified.
• Environment variables verified.
• Instance status is OPEN.
• Incoming messages work correctly.
• Outgoing messages always fail with ACK 463.
• WhatsApp Business sends messages normally from the phone.

Additional information:

• WhatsApp Business was reinstalled without restoring any backup.
• A brand-new Evolution instance was created after the reinstall.
• The problem persists even with the new instance.
• The logs indicate that Baileys successfully:

Question

Is ACK 463 a known issue related to recent WhatsApp protocol changes (LID/privacy tokens)?

Has this been fixed in a newer Evolution API release or Baileys version?

Any guidance would be greatly appreciated.