[AlmogCohen]

A message Baileys cannot decrypt (its CIPHERTEXT stub: no session, Bad MAC, invalid PreKey, message absent from the node) was skipped in messages.upsert with only a WARN, so a consumer had no trace of it. Circles saw four such group messages on one number between 2026-10-29 and 10-31 (all "No session found to decrypt message"); one came back through the retry receipt, three never did, and proving it took a read of the log archive.

Now it reaches the consumer as messages.undecryptable (subscribed as MESSAGES_UNDECRYPTABLE):

{ "key": { ...as Baileys gave it, a DM's @lid swapped into remoteJidAlt as on messages.upsert },
  "pushName": "...", "messageTimestamp": 1761934500, "chatKind": "group", "reason": "No session found to decrypt message" }

Never a body or the error's own text: reason is the constant Evolution matched. It is still not a messages.upsert (no storage, no chatbots). The readable copy a retry brings is a messages.upsert with the same key id, as before.

• d17b6648 test (red in CI): test/handlers/undecryptable-message.test.ts (both profiles), test/events/undecryptable-webhook.test.ts (/webhook/set accepts the name, per-instance and global delivery).
• ff43393e feat (green): the event in Events, EventController.events, the four instance.schema lists and every transport's global config; FORK.md.

No prisma/ change.

🤖 Generated with Claude Code