Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(message): note outbound media can be archived too

Yudhi Armyndharis095b6208232b
diff --git a/src/modules/message/message.service.ts b/src/modules/message/message.service.ts
index d28608176..a3651584b 100644
--- a/src/modules/message/message.service.ts
+++ b/src/modules/message/message.service.ts
@@ -506,11 +506,11 @@ export class MessageService implements PluginMessagePort {
/**
* Read a message's media: the archived file when one exists, else the inline copy persisted on
* the message row. The fallback is what makes media sent BY the account retrievable here — the
- * archive is written only on the inbound path, but outbound rows carry the payload inline: the
- * REST send persists it, wwjs downloads it for the own-send echo, and Baileys downloads it for
- * phone-composed fromMe messages (the Baileys API-send echo alone carries only a marker, which
- * the REST-persisted copy covers) — #1165. It also serves an inbound message whose archived file
- * was purged by retention while the inline copy lives on.
+ * archive covers outbound media only when CHAT_MEDIA_ARCHIVE_OUTBOUND=true, but outbound rows
+ * carry the payload inline: the REST send persists it, wwjs downloads it for the own-send echo, and
+ * Baileys downloads it for phone-composed fromMe messages (the Baileys API-send echo alone carries
+ * only a marker, which the REST-persisted copy covers) — #1165. It also serves an inbound message
+ * whose archived file was purged by retention while the inline copy lives on.
*
* Unlike status media (only ever an image, a video or a voice note), chat media includes documents
* a sender chose the type of — so the declared mimetype is echoed back only when it is inert, and the caller