# Version 2.6.3 Polling Unblock Fix

This patch fixes the case where customer SMS replies do not save to the dashboard and do not fire the AI assistant while TextBee polling is enabled.

## What the log showed

The webhook path was working: `MESSAGE_RECEIVED` was received, the inbound message was linked to the lead, saved, and the AI reply was attempted/sent.

The polling path, however, was repeatedly skipping messages because old deleted-lead suppressions were still active. It also called TextBee with a high received-message limit and hit a Cloudflare 524 timeout.

## Fixes

### 1. Deleted-lead suppression no longer blocks new unmatched replies

The poller now skips only exact old messages tied to deleted leads:

- exact provider message IDs from the deleted lead
- exact old inbound body hashes from the deleted lead
- messages clearly timestamped before the deletion when there is no active lead

If an active lead exists for the phone, unmatched customer replies are allowed through.

### 2. Polling limit default reduced

Default polling limit is now 10 instead of 25 to reduce TextBee API timeouts.

Recommended env:

```env
TEXTBEE_INBOUND_POLLING_ENABLED=true
TEXTBEE_INBOUND_POLLING_INTERVAL_SECONDS=30
TEXTBEE_INBOUND_POLLING_LIMIT=10
```

### 3. Polling failure logs are shorter

The app no longer dumps the full Cloudflare HTML page into `app.log` when TextBee returns a 524.

## After install

Clear old suppressions once:

```http
POST /admin/api/deleted-lead-suppressions/clear
```

Then retest.