Description
Sending messages to contacts with no prior conversation history fails with gRPC error 463 on GOWS engine (PLUS tier).
{
"statusCode": 500,
"exception": {
"message": "2 UNKNOWN: server returned error 463",
"code": 2
}
}
Environment
- WAHA version: 2026.3.1
- Engine: GOWS
- Tier: PLUS
- Platform: linux/x64
Root Cause
Per Baileys #2441 investigation:
- Error 463 =
NackCallerReachoutTimelocked — WhatsApp server-side "reach-out time-lock" rate limit
- Affects messages to unknown/cold contacts (no prior conversation)
- Caused by missing
tctoken and cstoken privacy fields in outgoing <message> nodes
- WhatsApp counts messages without these fields as "reaching out" and enforces time-based locks
- Confirmed: the fix was implemented in Baileys PRs #2257, #2339, and #2438
Expected Behavior
Messages should include tctoken/cstoken to avoid triggering the reach-out time-lock, matching official WhatsApp client behavior.
Actual Behavior
GOWS engine omits these tokens, causing 463 errors on cold contacts. Sending to existing contacts works fine.
Steps to Reproduce
- Create a GOWS PLUS session
- Attempt to send a message to a phone number that has never chatted with the session before
- Observe 500 error with gRPC error 463
Related

Description
Sending messages to contacts with no prior conversation history fails with gRPC error 463 on GOWS engine (PLUS tier).
{ "statusCode": 500, "exception": { "message": "2 UNKNOWN: server returned error 463", "code": 2 } }Environment
Root Cause
Per Baileys #2441 investigation:
NackCallerReachoutTimelocked— WhatsApp server-side "reach-out time-lock" rate limittctokenandcstokenprivacy fields in outgoing<message>nodesExpected Behavior
Messages should include
tctoken/cstokento avoid triggering the reach-out time-lock, matching official WhatsApp client behavior.Actual Behavior
GOWS engine omits these tokens, causing 463 errors on cold contacts. Sending to existing contacts works fine.
Steps to Reproduce
Related