The WebJS message_ack event provides (message, ack), but WAHA currently derives the acknowledgement from the message model and does not expose a useful failure reason. This makes a send that returns successfully from the API but later receives ACK_ERROR difficult to diagnose.\n\nRequested improvement:\n- Preserve the acknowledgement emitted with the event.\n- Include bounded ackReason details when WebJS provides an error message.\n- Provide a clear fallback when WhatsApp supplies no reason.\n- Log only message ID, destination, acknowledgement, and normalized reason.\n\nThis is particularly useful for intermittent delivery failures and contact/LID edge cases.
The WebJS message_ack event provides (message, ack), but WAHA currently derives the acknowledgement from the message model and does not expose a useful failure reason. This makes a send that returns successfully from the API but later receives ACK_ERROR difficult to diagnose.\n\nRequested improvement:\n- Preserve the acknowledgement emitted with the event.\n- Include bounded ackReason details when WebJS provides an error message.\n- Provide a clear fallback when WhatsApp supplies no reason.\n- Log only message ID, destination, acknowledgement, and normalized reason.\n\nThis is particularly useful for intermittent delivery failures and contact/LID edge cases.