Skip to main content

Common issues

If your symptom is specific to one feature, the troubleshooting section on that solution's page is more direct than this one.

Cross-cutting symptoms

SymptomProbable causeFirst fix
Nothing happens after publishingScript is in Head, not FooterMove it to Footer code and republish
window.WfAlgolia is undefinedTag missing, blocked by CSP, or type="module" absentVerify your setup
401 / 403 from algolia.netWrong key, or a key without the search ACLUse the Search-Only key
Results come from an unexpected indexAn ancestor supplies wf-algolia-index and the element inherited itSet explicitly on the wrapper
A numeric range filter never narrowsThe Algolia field is stored as a stringRe-index the field as a number
Sorting returns zero resultsThe replica name in your <option value="…"> does not match AlgoliaCheck Dashboard → Replicas
A filter search box does nothingThe facet is filter-only in AlgoliaSet it to searchable — see below
A static page never appears in resultsIt is not a CMS item, so no collection mapping indexes itIndex it with the Algolia Crawler

The searchable-facet trap

Searching within a facet's values uses Algolia's search-for-facet-values API, which only works when the attribute is declared searchable. A facet set to filter-only will filter correctly and fail silently at facet search.

In the Algolia dashboard: Configuration → Filtering and Faceting → Facets, then set the attribute to "Searchable (will return facets list)". Or in code:

index.setSettings({ attributesForFaceting: ['searchable(brand)'] });

What the console tells you

Every message is prefixed [wf-algolia]. The script warns and keeps going rather than throwing, so in most cases the warning is your only signal that something is misconfigured.

Configuration errors

These are thrown during startup, caught, and re-logged as [wf-algolia] Initialization failed: followed by the message.

MessageMeaning
Script tag missing data-app-id attributeNo element on the page matches script[data-app-id]
data-app-id and data-search-key are requiredOne of the two is present but empty

Content and rendering

MessageMeaning
Failed to clone hit:A result could not be rendered from your template
populateCard text error:A wf-algolia-text binding failed on one card
populateCard html error:A wf-algolia-html binding failed
populateCard image error:A wf-algolia-image binding failed
populateCard link error:A wf-algolia-link binding failed
populateCard snippet error:A snippet binding failed
Blocked unsafe URL:A field resolved to a URL scheme the script refuses to output

The populateCard warnings name the binding that failed, which is almost always a field name that does not exist on the record — check spelling and case against a record in the Algolia dashboard.

Detail pages

MessageMeaning
Detail page missing wf-algolia-indexThe detail wrapper has no index to query
Detail page: no objectID found in URL or attributesNothing identifies which record to load
Detail page: object not found forThe objectID was resolved but no record matched it

Recommendations

MessageMeaning
recommend section missing model, index, grid, or templateOne of the four required pieces is absent — the section renders nothing
recommend: unknown modelThe model name is not one Algolia recognises

Note the wording: a recommendation section needs all four of a model, an index, a grid and a template. Missing any one produces this single message.

Filters and hierarchy

MessageMeaning
Cycle detected in hierarchy atCascading filter groups reference each other in a loop
refreshChildGroup failed:A dependent filter group could not reload its values
refreshChildGroup (staged) failed:The same, in deferred-apply mode
standalone child re-scope failed:A standalone child group could not re-scope to its parent
facet-stat …A facet-stat element is misconfigured
static list …A statically authored filter list is misconfigured

Other

MessageMeaning
infinite-scroll loader rejected:The next page failed to load
Could not restart Webflow interactions:Webflow's IX2 could not be re-initialised after a render
Event handler error (…):One of your own WfAlgolia.on() handlers threw

Next