You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing issues and this isn't a duplicate
I'm on the latest released version (or noted my version below)
OpenWA version
0.27.1
Deployment
Docker Compose
Database
SQLite (default)
WhatsApp engine
whatsapp-web.js
What happened?
I am using OpenWA for automated WhatsApp messaging. Sessions are created successfully, QR code authentication works, and the connection becomes operational.
However, after sending automated messages, WhatsApp starts flagging the activity as spam. In some cases, recipient numbers may report suspicious messages, and the sending account may experience restrictions.
The issue seems to occur even when the WhatsApp session is properly authenticated and functional.
Expected Behavior
Sessions should be managed reliably without unnecessary reconnections.
Message delivery should provide clear status and error reporting.
The system should expose relevant information when WhatsApp restricts messaging.
Message queues should support controlled delivery and prevent accidental duplicate messages.
Session disconnections and authentication failures should be handled gracefully.
Actual Behavior
Sessions are created and authenticated successfully.
Automated messages are sent.
WhatsApp subsequently identifies the messaging activity as suspicious or spam.
The sending account may face restrictions or reduced messaging capabilities.
Investigation Required
Please investigate:
Whether the underlying messaging engine (Baileys or whatsapp-web.js) contributes to this behavior.
Whether session restoration or reconnection mechanisms can cause abnormal messaging activity.
Whether message retries can result in duplicate messages.
Whether the current implementation exposes WhatsApp delivery and restriction statuses correctly.
Whether there are known compatibility issues with recent WhatsApp Web updates.
Whether session lifecycle management can be improved.
Proposed Improvements
Improve session lifecycle and persistence management.
Add structured logging for outgoing messages and WhatsApp errors.
Implement proper message queue management.
Prevent unintended duplicate message submissions.
Expose delivery, failure, and restriction statuses.
Document known WhatsApp anti-spam limitations and risks.
Messaging engine: Baileys / whatsapp-web.js (to be confirmed)
Deployment: Self-hosted
Additional Information
This issue is not a request to bypass WhatsApp anti-spam protections or evade account restrictions.
The objective is to understand the technical causes, improve session and message management, and ensure that legitimate, consent-based notifications are handled reliably.
Any recommendations, known limitations, or suggested improvements would be appreciated.
Steps to reproduce
Deploy OpenWA on a self-hosted server.
Create a new WhatsApp session.
Scan the QR code using a WhatsApp account.
Wait until the session is successfully authenticated and connected.
Use the OpenWA API to send automated messages to multiple recipients.
Continue using the session for legitimate automated notifications.
Observe that WhatsApp starts flagging the sending activity as spam or suspicious.
In some cases, the sending account experiences restrictions.
Note: The exact API endpoint and payload depend on the OpenWA version and messaging engine being used.
Expected behavior
Successfully authenticated sessions should remain stable.
Legitimate automated messages should be processed reliably.
The application should provide clear delivery statuses and error details.
Failed messages should not be automatically duplicated.
WhatsApp restrictions should be detected and reported clearly.
Session reconnections should not trigger unintended message resubmissions.
Relevant logs
Currently, no specific error log has been identified at the moment the spam restriction occurs.
It would be helpful to have additional logging for:
Session creation and authentication.
Session disconnections and reconnections.
Outgoing message requests.
Message delivery acknowledgments.
Failed message attempts and retries.
WhatsApp-related errors and restriction events.
I can provide sanitized logs and additional technical details if needed.
Environment / additional context
Project: OpenWA
Deployment: Self-hosted
OS: To be specified
Node.js version: To be specified
Messaging engine: Baileys / whatsapp-web.js (to be confirmed)
Reverse proxy: To be specified
Session status: Successfully authenticated and connected
Use case: Automated WhatsApp notifications.
The main concern is that WhatsApp flags messaging activity as spam even though the session has been successfully created and authenticated.
I would like to understand whether this behavior is related to session management, the underlying messaging engine, message retries, or other technical limitations.
The goal is to improve reliability for legitimate, consent-based automated messaging without bypassing WhatsApp security or anti-spam protections.
This discussion was converted from issue #2027 on November 06, 2026 10:10.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Pre-flight
OpenWA version
0.27.1
Deployment
Docker Compose
Database
SQLite (default)
WhatsApp engine
whatsapp-web.js
What happened?
I am using OpenWA for automated WhatsApp messaging. Sessions are created successfully, QR code authentication works, and the connection becomes operational.
However, after sending automated messages, WhatsApp starts flagging the activity as spam. In some cases, recipient numbers may report suspicious messages, and the sending account may experience restrictions.
The issue seems to occur even when the WhatsApp session is properly authenticated and functional.
Expected Behavior
Sessions should be managed reliably without unnecessary reconnections.
Message delivery should provide clear status and error reporting.
The system should expose relevant information when WhatsApp restricts messaging.
Message queues should support controlled delivery and prevent accidental duplicate messages.
Session disconnections and authentication failures should be handled gracefully.
Actual Behavior
Sessions are created and authenticated successfully.
Automated messages are sent.
WhatsApp subsequently identifies the messaging activity as suspicious or spam.
The sending account may face restrictions or reduced messaging capabilities.
Investigation Required
Please investigate:
Whether the underlying messaging engine (Baileys or whatsapp-web.js) contributes to this behavior.
Whether session restoration or reconnection mechanisms can cause abnormal messaging activity.
Whether message retries can result in duplicate messages.
Whether the current implementation exposes WhatsApp delivery and restriction statuses correctly.
Whether there are known compatibility issues with recent WhatsApp Web updates.
Whether session lifecycle management can be improved.
Proposed Improvements
Improve session lifecycle and persistence management.
Add structured logging for outgoing messages and WhatsApp errors.
Implement proper message queue management.
Prevent unintended duplicate message submissions.
Expose delivery, failure, and restriction statuses.
Document known WhatsApp anti-spam limitations and risks.
Provide better diagnostics for developers.
Environment
Project: OpenWA
Repository: https://github.com/rmyndharis/OpenWA
Messaging: Automated WhatsApp messages
Session: Successfully authenticated
Messaging engine: Baileys / whatsapp-web.js (to be confirmed)
Deployment: Self-hosted
Additional Information
This issue is not a request to bypass WhatsApp anti-spam protections or evade account restrictions.
The objective is to understand the technical causes, improve session and message management, and ensure that legitimate, consent-based notifications are handled reliably.
Any recommendations, known limitations, or suggested improvements would be appreciated.
Steps to reproduce
Deploy OpenWA on a self-hosted server.
Create a new WhatsApp session.
Scan the QR code using a WhatsApp account.
Wait until the session is successfully authenticated and connected.
Use the OpenWA API to send automated messages to multiple recipients.
Continue using the session for legitimate automated notifications.
Observe that WhatsApp starts flagging the sending activity as spam or suspicious.
In some cases, the sending account experiences restrictions.
Note: The exact API endpoint and payload depend on the OpenWA version and messaging engine being used.
Expected behavior
Successfully authenticated sessions should remain stable.
Legitimate automated messages should be processed reliably.
The application should provide clear delivery statuses and error details.
Failed messages should not be automatically duplicated.
WhatsApp restrictions should be detected and reported clearly.
Session reconnections should not trigger unintended message resubmissions.
Relevant logs
Currently, no specific error log has been identified at the moment the spam restriction occurs. It would be helpful to have additional logging for: Session creation and authentication. Session disconnections and reconnections. Outgoing message requests. Message delivery acknowledgments. Failed message attempts and retries. WhatsApp-related errors and restriction events. I can provide sanitized logs and additional technical details if needed.Environment / additional context
Project: OpenWA
Deployment: Self-hosted
OS: To be specified
Node.js version: To be specified
Messaging engine: Baileys / whatsapp-web.js (to be confirmed)
Reverse proxy: To be specified
Session status: Successfully authenticated and connected
Use case: Automated WhatsApp notifications.
The main concern is that WhatsApp flags messaging activity as spam even though the session has been successfully created and authenticated.
I would like to understand whether this behavior is related to session management, the underlying messaging engine, message retries, or other technical limitations.
The goal is to improve reliability for legitimate, consent-based automated messaging without bypassing WhatsApp security or anti-spam protections.
All reactions