Cannot send status

[crawdz-cpu]

Welcome!

• Yes, I have searched for similar issues on GitHub and found none.

What did you do?

[BUG] /message/sendStatus endpoint hangs/timeout with no response
Environment

Evolution API Version: v2.3.7
Docker Image: evoapicloud/evolution-api:latest (pulled 5 weeks ago)
Integration Type: WHATSAPP-BAILEYS
CONFIG_SESSION_PHONE_VERSION: 2.24.6.77 (updated from 2.3000.1025062854)
Database: PostgreSQL 14
Cache: Redis 7-alpine
Server: Ubuntu (VPS)

Description
The /message/sendStatus/{instance} endpoint hangs indefinitely without returning any response (success or error). The request times out after waiting, and no error appears in the container logs.
Steps to Reproduce

Setup Evolution API with the following .env configuration:

envCONFIG_SESSION_PHONE_CLIENT=Evolution API
CONFIG_SESSION_PHONE_NAME=Chrome
CONFIG_SESSION_PHONE_VERSION=2.24.6.77
DATABASE_PROVIDER=postgresql
CACHE_REDIS_ENABLED=true

Create and connect an instance successfully (instance shows "state": "open")
Send status update request using any of these payloads:

Attempt 1 - With allContacts: true and empty statusJidList:
bashcurl -X POST "https://evo.bravomotor.id/message/sendStatus/ken"
-H "Content-Type: application/json"
-H "apikey: YOUR_API_KEY"
-d '{
"type": "text",
"content": "Test status",
"backgroundColor": "#06CF9C",
"font": 1,
"allContacts": true,
"statusJidList": []
}'
Result: Error 400 - "statusJidList does not meet minimum length of 1"
Attempt 2 - With allContacts: true without statusJidList:
bashcurl -X POST "https://evo.bravomotor.id/message/sendStatus/ken"
-H "Content-Type: application/json"
-H "apikey: YOUR_API_KEY"
-d '{
"type": "text",
"content": "Test status",
"backgroundColor": "#06CF9C",
"font": 1,
"allContacts": true
}'
Result: Request hangs indefinitely, no response
Attempt 3 - With specific JID in statusJidList:
bashcurl -X POST "https://evo.bravomotor.id/message/sendStatus/ken"
-H "Content-Type: application/json"
-H "apikey: YOUR_API_KEY"
-d '{
"type": "text",
"content": "Test status",
"backgroundColor": "#06CF9C",
"font": 1,
"statusJidList": ["xxxxxx@s.whatsapp.net"]
}'
Result: Request hangs indefinitely, no response
Expected Behavior
The API should return either:

Success response with message key/ID if status was posted successfully
Error response with clear error message if request failed

Example expected success response:
json{
"key": {
"remoteJid": "status@broadcast",
"fromMe": true,
"id": "..."
},
"message": {...},
"status": "success"
}
Actual Behavior

Request hangs/times out without any response
No error or info logged in docker logs evolution_api
Status does NOT appear in WhatsApp
Instance connection remains "state": "open" (no disconnection)

Container Logs
When monitoring logs with docker logs -f evolution_api while sending the request, there are:

✅ Normal message processing logs
✅ Session activity logs
❌ NO error or info about the /sendStatus request
❌ NO timeout error
❌ NO validation error

The request simply hangs with no trace in logs.
Additional Context
Instance Status (Before Test):
json{
"name": "xxx",
"connectionStatus": "open",
"ownerJid": "628xxxxxxxxxx@s.whatsapp.net",
"integration": "WHATSAPP-BAILEYS",
"disconnectionReasonCode": 401,
"disconnectionObject": "{"error":{"data":{"tag":"conflict","attrs":{"type":"device_removed"}},...}}"
}
Note: The instance shows a previous device_removed error but currently has connectionStatus: "open".
Related Issues Searched:

Issue #1090: allContacts: true not working
Issue #1229: TypeError with sendStatus
Issue #383: 400 error with contextInfo

What We Tried:

✅ Updated CONFIG_SESSION_PHONE_VERSION from 2.3000.xxx to 2.24.6.77
✅ Logged out and reconnected instances from phone
✅ Restarted container with new config
✅ Tried multiple payload formats
❌ All attempts result in hanging request

Workaround Needed
Is there a working payload format for posting WhatsApp Status/Stories via Evolution API v2.3.7, or should we update to a specific newer version?
Request
Please provide:

Confirmation if this is a known bug in v2.3.7
Recommended API version that has working sendStatus endpoint
Correct payload format if we're doing it wrong
Any required configuration we might be missing

Thank you!

What did you expect?

Expected Behavior

API returns immediate response (success or error), not hanging
If successful: Status appears in WhatsApp "My Status"
Response includes message key/ID or clear error message

What did you observe instead of what you expected?

Actual Behavior

Request hangs indefinitely - no response returned (not even after 60+ seconds)
No logs generated - zero error/info in docker logs evolution_api about the request
Status NOT posted - nothing appears in WhatsApp "My Status"
Instance stays connected (state: "open") but endpoint completely unresponsive

Screenshots/Videos

No response

Which version of the API are you using?

Environment

Evolution API Version: v2.3.7
Docker Image: evoapicloud/evolution-api:latest (pulled 5 weeks ago, Dec 2024)
Image Tag/Hash: Check with docker images evoapicloud/evolution-api
Integration Type: WHATSAPP-BAILEYS
CONFIG_SESSION_PHONE_VERSION: 2.24.6.77 (updated from 2.3000.1025062854)
Database: PostgreSQL 14
Cache: Redis 7-alpine
Server: Ubuntu VPS
Container uptime: 5 weeks (started ~Nov 26, 2024)

What is your environment?

Docker

Other environment specifications

No response

If applicable, paste the log output

No response

Additional Notes

No response