# Locate the failing layer first

Preserve materials and error evidence, then choose low-risk reversible checks.

## Quick troubleshooting table

| Symptom | Check first | Next step |
| --- | --- | --- |
| Site fails to load | Network and catalogue load status | Retry the same filters or read the GitHub catalogue |
| No Bot after download | Whether only a download occurred | Use the current host import preview and confirmation |
| Collection cannot import | Whether a file exceeds 200 Bots | Choose one role or release parts and check host total limits |
| Cannot read mail or files | Tools, account authorization, and readable materials | Provide sanitized materials or obtain required task access |
| English instructions in Chinese mode | Whether it is an attributed adaptation | Read adaptation notes and specify output language |
| SHA-256 mismatch | Whether card and download share a publication | Stop import and retrieve a consistent version or release snapshot |
| Complete-looking output lacks evidence | Whether sources and criteria are present | Add materials and list unknowns and conflicts |

If a file cannot be read, paste these two lines of public fictional text directly into the current Agent. Ask it to restate only the two facts with line numbers. Do not include customer materials.

```text
1 | Fictional project: Paper Plane; draft due Friday.
2 | Desktop tests passed; mobile tests not started.
```

If the restatement is correct, record “pasted text readable; original file reading still unverified” and save the result. Next check only the original file path, format, or access. If text also fails, preserve the error to investigate the model or session. Avoid blind retries under unchanged conditions and retain successful steps.

## Submit reproducible feedback

```text
Public feedback (sanitize first)
Page or public Bot ID:
Template version / language / content revision:
Host version (for import issues):
Time and minimal steps:
Expected result:
Actual result and error code:
Small public sample:
Sensitive-material handling status (if applicable; no sensitive values):
Exclude accounts, keys, private conversations, and customer materials.
```

Role detail feedback links prefill the public Bot ID, template version, and source. Review your additions before submission and keep complete private logs out of public feedback.

If sensitive material was pasted by mistake, address the exposure first: revoke or rotate credentials at the relevant service; deleting a chat does not invalidate credentials. For customer materials, delete them or restrict access in the actual service and establish the exposure scope. Report only handling status and necessary scope details, without repeating sensitive values.

## Preserve work before recovery

1. Save drafts, downloads, and necessary sanitized error details.
2. Separate site, format, host-import, model, and account problems.
3. Retry reading or reproduce with a small sample before considering a reset.
4. Follow current host documentation for running instances and record actual results.

## Three common misunderstandings

| Question | Answer |
| --- | --- |
| Does opening a source link install a Bot? | No. Original-site conditions and actions apply separately. |
| Does a working role certify account tasks? | No. Format checks differ from real-account acceptance. |
| Do Bots automatically share private memory? | Configurations do not transfer memory; hand off explicitly authorized packets. |

- [Public issue tracker](https://github.com/Harzva/awesome-bot/issues)

## Sources

Sources checked: 2026-10-25

- [Site and feedback notes](https://github.com/Harzva/awesome-bot/blob/main/README.md)
- [Import and verification scope](https://github.com/Harzva/awesome-bot/blob/main/INTEGRATION.md)
- [Digest mismatch handling](https://github.com/Harzva/awesome-bot/blob/main/docs/agent-integration.md)