Build a useful investigation brief
Select representative products
Choose products that contain the missing value, a neighboring value, and no value. Record category, variant, locale, and index timestamp. Use stable references so the comparison can be repeated without moving private product data into a new document.
Trace each boundary
Compare source field, indexed field, returned bucket, count, and rendered label. Check whether a facet limit, scope rule, null handling, or stale index explains the difference. Record a successful value path as a control and preserve negative evidence.
Package the finding
State the first disappearance, affected query scopes, and competing explanations. Recommend a bounded repair or follow-up with an observable result. Keep taxonomy decisions separate from transport or rendering problems so the next owner receives a tractable brief.
What to carry forward
The investigation is ready when one value can be followed from source to rendered facet or the missing boundary is explicit. Stop with a reproducible matrix and known limits. Do not call a facet configuration wrong when the source attribute never reaches the index.
Technical background: Adobe developer documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow