Summary
WordPress Connector pushes content to HolderChat immediately on sync, but your chatbot’s answers update only after a rebuild completes. Auto-sync uses a debounce window so rapid edits trigger one rebuild instead of many.
Prerequisites
- Connected WordPress site with HolderChat Connector
Sync vs rebuild
| Step | What happens | User-visible timing |
|---|---|---|
| Sync | Page text sent to HolderChat storage | Seconds |
| Rebuild | Knowledge index rebuilt for AI search | Minutes |
After editing a page, content may be synced but answers stay old until rebuild finishes.
Auto-sync (default: on)
When Sync content when pages/posts change is enabled:
- You publish, update, or trash a page/post
- Connector sends a delta sync to HolderChat
- Rebuild is debounced (not immediate by default)
- After quiet period, rebuild starts automatically
Debounce setting
| Setting | Default | Range |
|---|---|---|
| Debounce (seconds) | 90 | 30–600 |
Meaning: After the last content change, HolderChat waits this many seconds of no new changes before starting rebuild. Example: edit 5 pages in 2 minutes → one rebuild ~90s after the last save.
Manual sync
| Action | When to use |
|---|---|
| Sync all content now (Setup tab) | Force full resync; bypasses content dedup; starts rebuild |
Use after bulk imports, selection changes, or if auto-sync was off.
AI chunking
Use AI chunking when processing content splits long pages into semantic chunks for better retrieval.
| Mode | Speed | Quality | API usage |
|---|---|---|---|
| Off (whole page) | Faster | Good for short pages | Lower |
| On (AI chunks) | Slower | Better for long docs | Higher |
Help text: *Splits pages into semantic chunks with AI for better answers. Takes longer and uses more API credits than whole-page indexing.*
Applies on next sync or rebuild. Rebuild may wait until chunk jobs finish.
Batch sync
Large sites upload 75 pages per batch. Rebuild starts on the final batch of a full sync.
Daily sync
A daily cron runs a safety-net delta sync (staggered by site ID over 0–6 hours) to catch missed webhooks.
Failed sync retries
Failed syncs retry up to 3 times, 60 seconds apart.
Rebuild cooldown
Immediate rebuild may be skipped if another rebuild finished within 120 seconds, unless new content changes were detected.
Settings reference
| Setting | Default | Location |
|---|---|---|
| Auto-sync | On | Settings |
| Debounce | 90s | Settings |
| AI chunking | Off | Setup / Settings |
| Sync batch size | 75 pages | Internal (not user-editable) |
What triggers a rebuild
| Action | Rebuild timing |
|---|---|
| Create Chatbot | After full sync |
| Edit page (auto-sync on) | After debounce |
| Sync all content now | Immediately |
| Dashboard Rebuild Bot | Immediately (may queue) |
Limitations
- Debounce does not apply to manual Sync all content now
- Very large sites may stay in Building for 15+ minutes
- AI chunking adds queue time before rebuild
Troubleshooting
Symptom: Bot shows old text 5 minutes after edit
Cause: Debounce not expired or rebuild in progress.
Fix: Wait 90+ seconds; check status Building; use Sync all content now.
Symptom: Rebuild never starts
Cause: Auto-sync off and no manual sync.
Fix: Enable auto-sync or click Sync all content now.
Symptom: Sync errors in admin
Cause: Network or hub API failure.
Fix: Retries run automatically; check again after 3 minutes.