Incoming messages are dropped when the contact has disappearing messages enabled (v2.3.7, Baileys) — no messages.upsert, not stored #2773

Welcome!

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

What did you do?

Evolution API 2.3.7 (Docker), WHATSAPP-BAILEYS integration, webhook with MESSAGES_UPSERT enabled (working normally for all other chats).

1. From another phone, open the chat with the instance number and enable WhatsApp "Disappearing messages" (24 hours).
2. Send a text message (e.g. "hi, how much is it?").
3. Disable disappearing messages in the same chat and send another text message.

Reproduced on more than one instance on the same server, 100% of the time.

What did you expect?

Incoming messages in chats with disappearing messages enabled should be received like any other message (e.g. as ephemeralMessage wrapping the content, or unwrapped), stored, and emitted via messages.upsert to the webhook.

What did you observe instead of what you expected?

With disappearing messages ON: the message is visible on the phone linked to the instance, but Evolution API never receives it — no messages.upsert webhook call, and the message is not stored (it does not appear in the instance chat in the Manager, only the messages sent by the instance appear).

With disappearing messages OFF: new messages are received, stored and sent to the webhook normally.

Impact: for customer service integrations, any customer with disappearing messages enabled is silently ignored (no event, no error), so they never get a reply.

Screenshots/Videos

No response

Which version of the API are you using?

Versão / Version: 2.3.7

What is your environment?

Docker

Other environment specifications

Docker (Portainer), WHATSAPP-BAILEYS, PostgreSQL + Redis

If applicable, paste the log output

Can provide container logs captured at the moment of the test if needed.

Additional Notes

No response