Blocksify Pro index controls show whether Loop Filter counts are ready and provide safe actions for rebuilding or recovering them.
Before you start: Sign in with an administrator account.
Read the Status
- Go to Blocksify → Dashboard → Settings → Loop Filter.
- Wait for Status to load.
- Read Indexing, Pending jobs, Processing, Progress, and Lock before choosing an action.
| Readout | Meaning |
| Indexing | Enabled prepares option lists and counts. Disabled hides them; filtering results still use current content. |
| Pending jobs | The number of queued field builds. Zero means no work is queued. |
| Processing | Identifies the oldest queued field in the progress readout; None appears when the queue is empty. |
| Progress | Shows processed items against the total, such as 120 / 500. |
| Lock | Free means no batch holds the queue. Held means one has claimed it. Held, stale means that claim is older than expected. |
Rebuild and run jobs
Go to Blocksify → Dashboard → Settings → Loop Filter to use the Actions panel. With an idle queue it shows Rebuild index, Rebuild registry, and Disable indexing; Run jobs now and Cancel build appear only while jobs are pending.
- Rebuild index: clears prepared values and queues a complete background rebuild. Use it after a large import or widespread stale counts.
- Rebuild registry: rescans saved content for Loop Filter blocks and refreshes the known facets and fields. Use it after moving, importing, or bulk-editing pages with filters.
- Run jobs now: appears while jobs are pending and processes one batch immediately. Use it to check whether the queue can advance.
- Cancel build: appears while jobs are pending and asks the build to stop after its next batch while leaving queued jobs in place.
- Click the action that fits the issue.
- Wait for the notice, then reload the panel.
- Confirm that Pending jobs decreases and Progress advances.
Enable, disable, and recover indexing
Use the indexing switch for an intentional pause, and use the recovery action only for a genuinely stale lock.
- Disable indexing: appears with an idle queue and turns prepared facet options and counts off. Use it temporarily while diagnosing database load.
- Enable indexing: turns preparation back on and queues a rebuild. It replaces Disable indexing while the feature is off.
- Clear stuck jobs: empties the queue and releases its lock. It appears only when jobs are pending and Lock says Held, stale; a Free lock does not show this action.
Warning: Clear stuck jobs discards queued work. After using it, click Rebuild index to create a fresh queue.
When counts look wrong
Work through this checklist when a choice count is missing, behind, or different from the cards shown by the Target Loop.
- Go to Blocksify → Dashboard → Settings → Loop Filter and confirm Indexing is Enabled.
- If Pending jobs is above zero, click Run jobs now, reload the panel, and check whether Progress advances.
- If jobs keep waiting, confirm WordPress scheduled tasks can run and that loopback requests are not blocked by security, maintenance, or basic-auth settings.
- Click Rebuild index after large product or property imports, then allow the queue to reach zero.
- If saved filters are not being found, click Rebuild registry to rebuild the known facets and fields, followed by Rebuild index.
- Purge page, object, and CDN caches after the rebuild. Ensure filtered URLs keep their query strings rather than sharing one unfiltered cache entry.
- If Lock remains Held, stale, use Clear stuck jobs, then start a new rebuild.
For how URLs and counts fit together, read Filter URLs, shareable links and the results index. For persistent failures, use Loop Filter troubleshooting and the free plugin’s Common questions and troubleshooting.