Augeo AI Docs
SDKsSearch SDK

Troubleshooting

Diagnose missing panels, products, measurement, authentication, and styles.

Start with the loaded bundle version, actual API request, and selected results ownership mode. The browser Network panel distinguishes a setup error, a successful empty response, and an unavailable service section.

Prerequisites

Common symptoms

SymptomCheckFix
AugeoSearchSdk is missingScript load status and Content Security PolicyLoad the browser IIFE before mounting; permit the selected CDN
Nothing mountsExisting target elementPass an HTMLElement, not a selector or missing node
Field appears but panel stays closedonOpenChange callbackApply search.update({ open }) for every visibility request
No products after submissionPresence of onSearchSubmitRender results in the host route or omit that callback for panel mode
Product click does nothingonResultSelectProvide product navigation or selection behavior
Ask AI closes but no chat opensonAskAiConnect the callback to an assistant with its seed text
Missing catalog requestToken, open state, and results modeSupply a valid member bearer and submit in panel mode
Empty products with HTTP 200Products list and unavailable flagsDistinguish no matching products from a section marked unavailable
Auth errorsToken accessor and response codeRecover the member session, then retry or reopen
Requests target another environmentExplicit apiBaseUrl and bundle defaultsAlign the bundle and actual API override with your deployment
Failed recent removalOpaque ID and dismissal responseRetry the recents recovery control; verify persistence against the live service
No Remove controlRecent response lacks an IDUse a handler that provides opaque recent IDs
Completion callback does not runHost mode or canceled/failed requestUse panel mode and observe a current successful catalog response
No search.submitted on the root busBlank or fully redacted term, or an older bundleUse a current bundle and a nonblank term that survives sanitization. No host completion wiring is required
Submission is on the bus but not at the destinationConsent, mapping, allow list, or teardownAdmit the submitted type in the shared analytics configuration and keep the runtime alive through delivery
No search.performed after products showpresented was not called, or the keyword redacted to nullCall presented from the committed view. A fully redacted term emits nothing
search.performed fires before results renderReport ran on fetch or router completionMove the report to the committed products or empty state. search.submitted intentionally fires before results
Keyword is the typed prefixSelection used the field valueExecute and measure the selected suggestion keyword
Count equals total matchesresultCount used the match totalPass the displayed page item length
Schema rejects keyword lengthA host-built occurrence exceeded 200 charactersUse the SDK event. Do not build the occurrence yourself
TypeError from presentedPage or count is missing, fractional, or not a safe integerCorrect the facts and call presented again on that handle
Empty state emitted successCount was positive, or the host sent outcomePass 0 for an empty page. Do not send outcome
Failed search emitted emptyA failure was reported with count 0Show the error state and emit nothing. Cancel only a terminal failure
Repeat query emitted nothingThe cancelled handle was reusedSubmit again so the SDK creates a new execution
Stale coffee replaced teaThe old commit was not guarded by execution idIgnore delayed work for a superseded id
Panel close dropped host measurementThe host cancelled on onOpenChange(false)Keep the shell coordinator alive across panel closure
Route leave cancelled the new searchCleanup read the current idCancel only the id captured when that route started
Full page load lost the handleNavigation unloaded the SDKKeep the shell mounted, or implement a transfer before production
Results show but analytics is silentMapping or allow omits the performed typeAdd that type to mapping and allow. Keep the root listener only
Second event on rerenderA rerender was treated as a new searchDuplicate commits are ignored. Do not submit again on rerender

Script, API, and browser policy

Inspect window.AugeoSearchSdk.version to identify the loaded build. The global .apiBaseUrl reports the bundle default; inspect requests when the instance overrides that origin. Permit the CDN in script-src, the selected API in connect-src, and product image origins in img-src. Ensure the API allows your host origin and Authorization header. Do not disable browser policy checks to hide an integration failure.

Styles and sizing

The bundle installs its design-system styles and CSS reset inside Shadow DOM. A global host reset does not replace the widget's internal reset. A separate design-system package download is not required for a script embed.

Confirm the release URL and computed styles when buttons, fields, or product rows appear unstyled. Remove obsolete SDK copies before testing a newly released bundle. Give the host mount enough width and verify both sides of the 767-pixel breakpoint. Use branding.theme for supported theme overrides rather than depending on internal element classes.

Recover and change options

Section failure controls retry that section's request. Authentication recovery still requires your host to supply a valid credential. Changing a token does not trigger an automatic retry of the currently failed section.

update({ onSearchSubmit: undefined }) keeps the existing callback. To return to panel results, destroy the instance and recreate it without onSearchSubmit. The same rule applies when restoring automatic presentation after an explicit override.

Measurement lifetime

Submission counts are owned by the SDK and do not need a host completion handle. Use the separate performed event when you need confirmed result facts. The lifetime rules below apply to that result measurement.

A throwing analytics adapter must not replace the rendered results. That failure also must not make the execution eligible again. If the products are correct and no event arrived, record a telemetry failure separately. Closing the panel is not abandonment of a host search. Leaving the results route is. An old route must cancel only the id it captured. Full document navigation cannot keep an in-memory handle. Do not treat that flow as accepted until a transfer exists. Compare the symptom with Concrete outcomes.

Gather useful evidence

Record the bundle version, configured API origin, viewport, results mode, and callback name. Include HTTP status and sanitized response shape when a request fails. Label the run live or controlled. Include execution id, displayed count, event count, and schema result. Live means the deployed host and published bundle. Controlled means a fixture, local bundle, or injected catalog. Exclude Authorization headers, member tokens, typed queries, and recent text from shared diagnostics. The sanitized keyword may be recorded as the analytics field.