Canonical: https://botbento.com/docs/troubleshooting/
Format: Markdown representation of the public HTML page.

BOTBENTO / DOCUMENTATION

# Troubleshoot settings and connections

Check the returned state before repeating a change.

- [Documentation](/docs/)
- [Account and connections](/docs/account-and-connections/)
- [Permissions](/docs/permissions/)
- [Troubleshooting](/docs/troubleshooting/)

## A setting is missing

Use Settings search or the section chooser. Search terms such as username can find a control without its section name. Sections containing only informational notes are hidden from the section list and search.

Availability also depends on your build, account and configured services. An unavailable security control does not become usable by reopening it. Read the guidance shown beside it.

## A profile save failed

Read the error beside the affected name or username field. Wait for an in-progress operation, check the returned state and use the offered retry. Do not treat the text still visible in an editor as proof the server saved it.

After a connection interruption, inspect the account state and confirmation before beginning another change. Preserve the error wording for a problem report, with personal details removed.

## Email verification did not finish

The hosted email-change flow needs both inboxes and a capable WorkOS account. Verify the current inbox first, then the new one. If the new-code send failed, use its retry; if the request expired, start again.

If security details could not load, retry the read before changing them. A rejected or unavailable address does not authorize merging accounts. Cancel can abandon a pending change. Never paste verification codes into a problem report.

## A setup entry did not connect a service

ChatGPT / OpenAI opens model settings; Gmail opens a filtered catalog. Those entries are navigation. Check the actual provider/app setup and returned state for authentication, permissions and assignment.

Runtime availability, execution permission and Computer pairing remain separate. A local healthy indicator or screenshot is not evidence of a live provider response. Avoid granting unrelated access to try to repair a missing permission.

## Report a persistent failure

Use Report a problem in Settings when available, or the public contact page. Include the affected control, what you expected, what happened, the visible error and whether the problem follows an interrupted operation.

Omit credentials, verification codes, cookies, private messages and other account data. A submitted report is not proof the failure is fixed; check the returned result when a correction is available.

[Contact BotBento](/contact/)

Last reviewed: 19 October 2026. Maintained with AI assistance and checked against implemented behavior. Build, account, provider and native-device availability remain separate.