Skip to navigation

Troubleshooting and FAQ

6MM AI Customer Support · Tenant guide

View as Markdown

Console and visitor support

SymptomCheck first
A menu is missingAccount role and tenant service availability
Widget does not openGenerated script URL, App Key, allowed domain and browser errors
Bot does not use the large modelActual matched step, intelligent-service switches and relevant configuration
An answer uses old rulesSource article, published status, FAQ text, translation and retrieval state
Translation is absentTarget language, translation switch, saved translation and service/balance availability
Vector generation failsService availability and retrieval status; avoid repeatedly rebuilding without identifying the failure
A contact field is emptyWhether that field was actually collected; distinguish contact and entry email

MCP connection and calls

SymptomNext step
Opening the endpoint in a browser returns an errorIt is a protocol endpoint, not a login page; add it to a compatible MCP client
Authorization cannot startVerify the exact endpoint, client’s Streamable HTTP/OAuth support and browser login flow
Unauthorized or expired connectionCheck revocation and expiration; reconnect through the application
A tool is missing or access is deniedCheck the authorizing account role and record scope; refresh the tool list
Awaiting approvalOpen the returned approval link and review it in the backend
Content changedRead the latest record, preview again and submit a new intended operation
Request timed outQuery the operation status before retrying or assuming failure
No write logDistinguish a read, pending approval and completed write; check filters in Operation Logs

Before contacting support

Collect the time and timezone, affected tenant/account, page or tool name, operation ID where available, and the exact error. Include a redacted screenshot or steps to reproduce. Do not send passwords, verification codes, bearer tokens or signing secrets.

Try a small test record when diagnosing writes. Verify the result and clean up only the test data you created, using the normal confirmation flow where required.