> For the complete documentation index, see [llms.txt](https://support.whapi.cloud/help-desk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.whapi.cloud/help-desk/troubleshooting/why-channel-keeps-disconnecting.md).

# Why channel keeps disconnecting

It looks like this: the number is disconnected from the channel, the channel status changes to **QR**, and everything stops. The channel will not come back on its own — you need to connect the number again, either by scanning the QR code or by using a pairing code.

Here is why this happens and what you can do about it.

### How often it happens points to the cause

| How often                                                       | Most likely cause                            |
| --------------------------------------------------------------- | -------------------------------------------- |
| Roughly every two weeks                                         | The phone has not been opened for 14 days    |
| From the number's first days                                    | The number is new and has not been warmed up |
| Day after day, and you did not unlink the device from the phone | WhatsApp does not trust the session          |
| Once, with no pattern                                           | The linked device was removed from the phone |

### Cause 1. The phone has not been opened for 14 days

The most common one. WhatsApp disconnects all linked devices, including the API session, if the primary phone has not opened the app for 14 days.

**What to do:** open WhatsApp on the phone every 10–12 days and send a couple of messages manually.

### Cause 2. The number is new and has not been warmed up

WhatsApp checks a new number far more closely than an established one: the same load that is perfectly normal for an old number looks suspicious coming from a fresh one. Connecting a new number to the API without warming it up is not a good idea — WhatsApp often disconnects such numbers.

On a new number this usually shows up not as a block, but as repeated resets: the channel loses authorization after a few hours or days. Treat it as an early warning — if the number keeps carrying the same load without a warm-up, it can escalate to a full block.

**What to do:** warm the number up — use it manually from the phone on the first day, then increase activity gradually, and only after that move it into automation ([Warming Up New Phone Numbers](https://support.whapi.cloud/help-desk/blocking/warming-up-new-phone-numbers-for-whatsapp-api)). Keep volumes low while the number is young. Warming does not stop resets instantly — it builds the trust whose absence causes them, so the earlier you start, the sooner they stop.

### Cause 3. WhatsApp does not trust the session

WhatsApp may reset a session pre-emptively if the number's behaviour looks unnatural to it: a sharp rise in message volume, unusual activity, other web agents connecting to the account.

On its own this is rare. But if the resets repeat day after day and you did not unlink the device from the phone, this is almost always the reason.

**What to do:** return to the volumes that are normal for this number, check whether any unnecessary web agents are connected, and do not message people who are not expecting you. More on this: [How to Not Get Banned](https://support.whapi.cloud/help-desk/blocking/how-to-not-get-banned).

### Cause 4. The linked device was removed from the phone

The API session can be switched off directly from the phone, in the list of linked devices — sometimes by accident.

### What we can see on our side

WhatsApp does not tell us why it ended a session: the channel logs show that the session dropped, but not what caused it. That is why the cause is worked out from indirect signs, above all from how often the resets happen.

### If the resets continue

Look at what was happening right before the reset — both on the phone and in your own integration. This is often where the answer turns up: a script that misfired and sent a hundred messages instead of ten is enough for WhatsApp to react to the spike.

If that leads nowhere, write to us — we can change the channel's proxy IP or region. It is not a guaranteed fix, but in practice it often helps once the other causes have been ruled out.

### How to reduce the risk

* Open WhatsApp on the phone every 10–12 days.
* Warm new numbers up before connecting them to the API.
* Avoid sharp spikes in volume.
* Use a proxy that matches the phone's region — a [residential one](https://support.whapi.cloud/help-desk/blocking/using-residential-proxies-with-whapi.cloud).

### See also

* [Warming Up New Phone Numbers for WhatsApp API](https://support.whapi.cloud/help-desk/blocking/warming-up-new-phone-numbers-for-whatsapp-api)
* [Automatic warm-up module](https://support.whapi.cloud/help-desk/tools/automatic-warm-up-module)
* [How to Not Get Banned](https://support.whapi.cloud/help-desk/blocking/how-to-not-get-banned)