Troubleshoot a missing page, answer, or product in Humind
Identify whether a missing result belongs to permissions, Knowledge, catalog, Agent configuration, deployment, or Helpdesk publication Follow a safe workflow, verify the customer-facing result, and isolate common problems.
Identify whether a missing result belongs to permissions, Knowledge, catalog, Agent configuration, deployment, or Helpdesk publication This guide keeps the work focused on cross-product troubleshooting and provides a repeatable path that a new Humind user can follow without changing unrelated configuration.
When customer-facing behavior is missing or stale, isolate the layer that owns it: source content, visibility, indexing, Agent configuration, deployment, permissions, or publication. Checking one layer at a time produces a useful diagnosis and avoids broad changes that hide the original cause.
Before you begin
Access: Read access to the affected area is required. Ask an administrator to confirm hidden areas without broadening access unnecessarily.
- Capture the exact URL, prompt, product, Agent, company, channel, and time.
- State the expected result in one sentence.
- Reproduce in a fresh session before editing.
Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.
Step-by-step workflow
Confirm the scope and current state
Classify the symptom as navigation or permission, Knowledge answer, catalog product, Agent behavior, live deployment, or Helpdesk publication.
- Confirm the active company and Agent before editing.
- Record the current state so the result can be compared after the change.
- Stop if the screen or permission does not match the intended task.
Prepare the change
Inspect the earliest owning layer: effective permission, authoritative source and lifecycle, source sync, indexing, Agent configuration, allowed domain, or active publication.
- Use the smallest change that completes the customer task.
- Keep authoritative information in its owning source.
- Review labels, dates, language, and customer-visible wording before saving.
Save and allow required processing to finish
Correct one layer only and wait for its save, sync, indexing, deployment, or publication transition to complete.
- Wait for the interface to confirm that the change is saved.
- If synchronization, indexing, or publication is required, wait for its final state.
- Reload the area and confirm the saved values persist.
Test the complete customer journey
Repeat the original scenario and one boundary case, then document the root cause and a regression check.
- Use a fresh session and a realistic customer scenario.
- Check desktop and mobile when the result appears on a storefront.
- Capture the exact failing step if the outcome differs from the expectation.
Important limits and operating notes
- A successful save confirms persistence, not every downstream synchronization or public update.
- Workspace permissions can hide an area or allow reading without allowing changes.
- Do not copy volatile catalog, account, or customer facts into narrative content as a workaround.
- Test only supported capabilities that are visible and configured for the current company.
- Keep changes in cross-product troubleshooting separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.
Verify the result
- The issue is reproducible or the differing context is known.
- One owning layer explains the symptom.
- The original scenario works after a focused correction.
- No unrelated access, content, catalog, or publication changed.
Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.
Troubleshooting
The symptom occurs only on the live site
Compare deployed Agent, domain, market, language, embed count, and conversation history with the test surface. A passing workspace test does not prove the live installation.
Several layers look wrong
Start with permissions and authoritative source data, then move downstream in order. Record each state before changing it so one correction does not hide another failure.