Troubleshoot and protect private information
Find the right next action for common problems and share only the information needed to investigate them.
Start with the current state
| Problem | Check first |
|---|---|
| I cannot find my bots | Confirm the signed-in account and return to Your bots |
| The build is taking longer than expected | Open its current work log and Activity before starting another request |
| Generated code has unresolved checks | Open Review checks and follow the current finding: complete setup, test a feature, or repair confirmed code problems |
| Publishing is blocked | Read readiness for build, account, database, configuration, or billing requirements |
| Connected but no reply | Check the published version, hosting health, permissions, and reply policy |
| My edit is missing in the live bot | Compare saved and published versions and review Publish update |
| The bot answers with old website facts | Review saved citations, freshness, integration, and publication |
| Available balance fell before work finished | Review reservations and recorded usage in Billing |
| Payment completed but the balance has not updated | Refresh Billing and retain the checkout reference before contacting support or paying again |
| An expected email did not arrive | Confirm the verified email, notification preference, and spam folder; read the current project result |
| Project files appear missing | Confirm the account and project, then review saved versions and recovery before replacing files |
Give a reproducible example
Include the project identity, platform, approximate time, steps, and expected versus actual result. Say whether it repeats. Share a cropped status screenshot or harmless example message, removing customer details.
Use Check & fix with BOTS SI to investigate and attempt a safe repair of confirmed code problems. Choose Check only for a free explanation of saved evidence without changes. A new build, account reconnection, hosting recovery, payment, and source change solve different problems; the current evidence helps you choose.
Use the right place for sensitive details
- Put platform credentials only in dedicated connection fields. Do not paste passwords, private tokens, or wallet recovery phrases into prompts or attachments.
- Give the builder public or anonymized examples. Remove personal details from screenshots and files before sending them.
- Ask for customer record isolation, owner permissions, and deletion behavior appropriate to your bot. Verify those journeys using separate accounts.
- Review source and public settings before private sharing, featured submission, or changing repository visibility.
For account or data requests without an available control, use the product’s support contact. Describe the request without sending credentials. Retention, export, or recovery outcomes need confirmation for the specific request.