Indexing runs as a background queue, so give it a few minutes first — large content sets legitimately take a while, and the Index tab shows progress as chunks complete.
If it genuinely stalls, Wyregraf detects the stuck queue on the embedding's Index tab and offers to clear it; clear the queue and start the index run again. A queue that stalls repeatedly usually has one of two causes:
- Provider errors — an invalid API key or an exhausted quota fails every chunk. See API key and quota errors.
- Background processing being blocked — WordPress background jobs depend on WP-Cron, so aggressive caching or a host that blocks loopback requests can keep the queue from ticking. Your host can confirm whether WP-Cron is firing.
The queue is safe to clear and re-run — indexing is repeatable, and re-running simply rebuilds the chunks.
