Establish what is happening
Compare source and buckets
Choose a category and query, then list the attribute values present in eligible products beside the values returned to the interface. Include nulls and values with small membership. Keep the query and index state attached to the comparison.
Classify the omission
Decide whether a value is missing from source data, filtered out by scope, collapsed by a limit, or absent because no matching product remains. Compare one broad query with one narrow query so dynamic behavior is not mistaken for a defect.
Set the coverage boundary
Record which facet values belong in scope, which are intentionally hidden, and what evidence is needed for the remainder. Keep a missing-value example visible. Do not promise complete attribute coverage when the catalog itself is incomplete.
What to carry forward
The triage output is a coverage map naming source values, returned values, scope rules, and data gaps. Stop when the team can explain an omitted value from evidence. If the cause is still unclear, route the smallest source-versus-index comparison instead of changing the UI.
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