Troubleshooting guide

Troubleshoot a Comments embed

Confirm the stylesheet import and a real user.id from the session. An empty user shows “Sign in to join the discussion.”
For Hosted, confirm appId is the published cma_ id and NEXT_PUBLIC_BSW_COMMENTS_PUBLISHABLE_KEY is the envLine from ensure_comment_test_publishable. A secret in that variable will fail as an invalid publishable key.
If the hint asks for an author token, the key is live or the app set requireAuthorToken. Call the server route in the Next.js guide. Do not mint in the client.
“You do not have access” on screen means the token aid does not match user.id, or the token is expired or malformed. Renew it. A 403 on write with a matching id means the permission is missing.
A 404 with “The requested resource was not found.” means the token's app, tenant, type, or resource does not match the row. Check you did not send tenant acme with a token minted for tenant other.
409 stale_version or thread_resolved: reload or reopen, and keep the draft. Reuse an operationId only for the same payload.
403 quota_exceeded is the 1 GiB meter for that environment. Delete text or export, then retry the growing write. Reads still work.
MCP: if a tool name is the Chat name list_apps, switch to list_comment_apps on server bootstrapware-comments.