Browse documentation
Find where the connection stopped
Use separate observations instead of one ambiguous connected badge.
Sign-in is unavailable
For the hosting profile, check the server-only MongoDB connection, database name, auth secret and configured origin. Inspect a safe request/error ID without logging credentials. A visible signup form or an active Atlas cluster does not prove the app can connect. Email verification and recovery require the service’s configured, verified mail delivery; a request being accepted does not prove inbox arrival.
The local inbox does not open
For the default local profile, keep pnpm dev running and check http://127.0.0.1:4010/health. A worker heartbeat is separate from API availability. Use pnpm demo:seed only when you intend fictional records; a fresh workspace should be empty.
Configuration exists but no customer does
Open Help in the selected build. Configuration fetch alone does not register an installation. Compare the public config ID and app/environment. Do not mix a production ID with a development support session.
A reply is stored but not visible
Refresh the native foreground conversation. Check operator commit, SDK fetch, visible native text and the exact development display acknowledgement separately. A local successful exchange does not establish your host build or a hosted/push route.
A reply was not sent
Keep the draft. Retry a recoverable or lost response with the original request identity and complete payload. On a stale Send and resolve conflict, read the newer message first. At a new-thread limit, use Copy or the app’s email fallback.
A theme does not change
Save and publish for the exact app/environment. A host lock can override a published value. An older SDK may keep its compatible fallback. Inspect the actual host rather than the website’s illustrative preview alone.