Welcome!
What did you do?
We configured an instance (taha_store) using the WHATSAPP-BAILEYS integration in Evolution API v2.3.7 running on a cloud VPS.
The instance was handling strictly reactive, inbound customer service requests (price queries and warranty questions). We implemented human typing presence simulation (sendPresence: composing with a 2-second delay) and anti-spam debouncing (2.5s window). No bulk/mass messages or broadcasts were ever sent.
What did you expect?
We expected the multi-device connection to remain stable and connected continuously for legitimate inbound customer service conversations.
What did you observe instead of what you expected?
The instance suddenly disconnected with error code 401 (conflict: device_removed).
On the physical phone, WhatsApp logged out of the linked devices session and displayed a 24-hour temporary restriction stating that an unofficial application was detected.
Error payload from /instance/fetchInstances:
{
"instance": "tastore",
"connectionStatus": "close",
"integration": "WHATSAPP-BAILEYS",
"disconnectionReasonCode": 401,
"disconnectionObject": {
"error": {
"data": {
"tag": "conflict",
"attrs": {
"type": "device_removed"
}
},
"isBoom": true,
"isServer": false,
"output": {
"statusCode": 401,
"error": "Unauthorized",
"message": "Stream Errored (conflict)"
}
}
}
}
### Screenshots/Videos
_No response_
### Which version of the API are you using?
v2.3.7
### What is your environment?
Windows
### Other environment specifications
Docker
- OS: Ubuntu 22.04 LTS (Cloud VPS)
- Node.js version: v20+ / Docker latest
- Integration: WHATSAPP-BAILEYS
- Country / Region: Libya (+218)
### If applicable, paste the log output
_No response_
### Additional Notes
_No response_
Welcome!
What did you do?
We configured an instance (
taha_store) using theWHATSAPP-BAILEYSintegration in Evolution API v2.3.7 running on a cloud VPS.The instance was handling strictly reactive, inbound customer service requests (price queries and warranty questions). We implemented human typing presence simulation (
sendPresence: composingwith a 2-second delay) and anti-spam debouncing (2.5s window). No bulk/mass messages or broadcasts were ever sent.What did you expect?
We expected the multi-device connection to remain stable and connected continuously for legitimate inbound customer service conversations.
What did you observe instead of what you expected?
The instance suddenly disconnected with error code
401 (conflict: device_removed).On the physical phone, WhatsApp logged out of the linked devices session and displayed a 24-hour temporary restriction stating that an unofficial application was detected.
Error payload from
/instance/fetchInstances:{ "instance": "tastore", "connectionStatus": "close", "integration": "WHATSAPP-BAILEYS", "disconnectionReasonCode": 401, "disconnectionObject": { "error": { "data": { "tag": "conflict", "attrs": { "type": "device_removed" } }, "isBoom": true, "isServer": false, "output": { "statusCode": 401, "error": "Unauthorized", "message": "Stream Errored (conflict)" } } } } ### Screenshots/Videos _No response_ ### Which version of the API are you using? v2.3.7 ### What is your environment? Windows ### Other environment specifications Docker - OS: Ubuntu 22.04 LTS (Cloud VPS) - Node.js version: v20+ / Docker latest - Integration: WHATSAPP-BAILEYS - Country / Region: Libya (+218) ### If applicable, paste the log output _No response_ ### Additional Notes _No response_