[BUG] WhatsApp account gets temporarily restricted after 1–2 days of usage with Evolution API v2.3.7 (QR Code blocked for 24h)

[romariormr]

Welcome!

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

What did you do?

Bug Description

After using Evolution API v2.3.7 normally for 1–2 days, my WhatsApp account gets temporarily restricted by WhatsApp itself.
During this restriction, WhatsApp blocks new device mirroring via QR Code for ~24 hours and shows a countdown timer in the mobile app.

This restriction does NOT happen immediately after pairing. It only happens after some time of normal usage.

The warning shown in the official WhatsApp app is:

"Your account is currently restricted. It looks like you may be using tools that do not follow our Terms to send automated or bulk messages."

While the restriction is active:

• I can only reply to existing chats
• I cannot start new conversations
• I cannot pair again via QR Code
• Evolution API loses the connection and cannot reconnect

After the countdown ends, pairing works again, but after some time the account gets restricted once more.

---

Steps to Reproduce

1. Deploy Evolution API v2.3.7 using Docker Swarm.
2. Create a new instance using QR Code (Baileys connection).
3. Scan the QR Code and successfully connect the WhatsApp account.
4. Use the instance normally for 1–2 days.
5. After this period, WhatsApp applies a temporary restriction.
6. QR Code pairing is blocked for ~24 hours.
7. Evolution instance disconnects and cannot reconnect during the restriction.

---

✅ Expected Behavior

• The WhatsApp account should remain connected indefinitely.
• QR Code pairing should continue to work normally.
• Evolution API should not trigger account restrictions with regular usage.

---

❌ Actual Behavior

• After 1–2 days of usage:
  • WhatsApp shows a temporary restriction warning.
  • QR Code pairing is blocked for ~24 hours.
  • New chats cannot be started.
  • The Evolution instance disconnects and cannot recover.
• After the restriction expires, everything works again — until the next restriction.

---

Environment

• Evolution API Version: v2.3.7
• WhatsApp Web Version: 2.3000.1030444778
• Deployment: Docker Swarm (compose v3.7)
• CPU: 4 cores
• Memory: 6144 MB
• Node.js: [not specified in container]
• Database: PostgreSQL
• Cache: Redis (disabled at moment)
• Storage: MinIO (S3 enabled)
• Provider Integrations:
  • Typebot ✅
  • Chatwoot ✅
  • OpenAI ✅
• Connection Type: Baileys (QR Code)
• WhatsApp App: Android
• Language: pt-BR

---

Relevant Docker Environment Variables

CONFIG_SESSION_PHONE_CLIENT=WhatsAPI
CONFIG_SESSION_PHONE_NAME=chrome
CONFIG_SESSION_PHONE_VERSION=2.3000.1030444778
QRCODE_LIMIT=1902
CACHE_REDIS_ENABLED=false
DATABASE_ENABLED=true
S3_ENABLED=true
TYPEBOT_ENABLED=true
CHATWOOT_ENABLED=true
OPENAI_ENABLED=true
RABBITMQ_ENABLED=false


### What did you expect?

- The WhatsApp account should remain connected indefinitely.
- QR Code pairing should continue to work normally.
- Evolution API should not trigger account restrictions with regular usage.

### What did you observe instead of what you expected?

- CPU: **4 cores**
- Memory: **6144 MB**

### Screenshots/Videos

<img width="720" height="1600" alt="Image" src="https://github.com/user-attachments/assets/d2b0b33c-1440-4b1b-aa50-5ebfe8ee1bce" />

### Which version of the API are you using?

v2.3.7

### What is your environment?

Docker

### Other environment specifications

_No response_

### If applicable, paste the log output

_No response_

### Additional Notes

_No response_

[mmojadad]

Hi
I had exactly the same experience right after upgrading to version 2.3.7, with the only difference being that it happened to me after sending messages to 2 contacts.
In version 2.3.6, for example, I had never encountered anything like this with similar behavior.

[juniorerivaldo]

o mesmo aqui, mais na 2.3.6 enviei 2 mensagens e já derrubou uma instancia, a outra até que durou enviou 54 mensagens.

[dannyokec]

I am just getting to know of evolutionapi does this mean we are not safe