Describe the bug
When sending a WhatsApp message using the sendText endpoint with the GOWS PLUS engine, the API returns a 500 error with the following exception:
"message": "2 UNKNOWN: no LID found for 525537135075@s.whatsapp.net from server"
Environment
- Version:
2026.5.1
- Engine:
GOWS
- Tier:
PLUS
- Platform:
linux/x64
API Request
Endpoint
Request Body
{
"session": "session_Moksha_1768221582636",
"chatId": "525537135075@c.us",
"text": "Hello there."
}
Actual Result
API returns HTTP 500 error.
Error Logs
{
"statusCode": 500,
"timestamp": "2026-05-26T07:32:11.213Z",
"exception": {
"message": "2 UNKNOWN: no LID found for 525537135075@s.whatsapp.net from server",
"code": 2,
"details": "no LID found for 525537135075@s.whatsapp.net from server",
"name": "Error"
}
}
Stack Trace
Error: 2 UNKNOWN: no LID found for 525537135075@s.whatsapp.net from server
at callErrorFromStatus (/app/node_modules/@grpc/grpc-js/build/src/call.js:32:19)
at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client.js:193:76)
at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:367:141)
at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:327:181)
at /app/node_modules/@grpc/grpc-js/build/src/resolving-call.js:135:78
at process.processTicksAndRejections (node:internal/process/task_queues:84:11)
Expected Result
The message should be delivered successfully to the WhatsApp contact without returning a 500 error.
Additional Notes
-
The chatId used is:
-
Internally, the engine appears to resolve it to:
525537135075@s.whatsapp.net
-
The issue may be related to LID/contact resolution on the WhatsApp server side.

Describe the bug
When sending a WhatsApp message using the
sendTextendpoint with the GOWS PLUS engine, the API returns a500error with the following exception:Environment
2026.5.1GOWSPLUSlinux/x64API Request
Endpoint
Request Body
{ "session": "session_Moksha_1768221582636", "chatId": "525537135075@c.us", "text": "Hello there." }Actual Result
API returns HTTP
500error.Error Logs
{ "statusCode": 500, "timestamp": "2026-05-26T07:32:11.213Z", "exception": { "message": "2 UNKNOWN: no LID found for 525537135075@s.whatsapp.net from server", "code": 2, "details": "no LID found for 525537135075@s.whatsapp.net from server", "name": "Error" } }Stack Trace
Error: 2 UNKNOWN: no LID found for 525537135075@s.whatsapp.net from server at callErrorFromStatus (/app/node_modules/@grpc/grpc-js/build/src/call.js:32:19) at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client.js:193:76) at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:367:141) at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:327:181) at /app/node_modules/@grpc/grpc-js/build/src/resolving-call.js:135:78 at process.processTicksAndRejections (node:internal/process/task_queues:84:11)Expected Result
The message should be delivered successfully to the WhatsApp contact without returning a
500error.Additional Notes
The
chatIdused is:Internally, the engine appears to resolve it to:
The issue may be related to LID/contact resolution on the WhatsApp server side.