> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superun.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Don't just say “it doesn't work”

> Reproduce first, then describe the page, steps, actual vs expected result.

When a page won’t open, a button does nothing, or submit fails, don’t just say “this feature is broken — please fix it.”

That only states the outcome. The same “broken” can mean different root causes — and different places to look.

If you don’t clarify, Su Xiaoqiang may scan navigation, forms, login, data save, and layout while guessing which step failed. Wrong guesses mean more rounds and more credits.

### Save credits: reproduce, then describe

1. Walk the normal entry path again and note which step fails.
2. Describe what you **actually see** — e.g. endless loading, phone-format error, jump back to login — not just “broken.”
3. State the expected result (sometimes it’s not a crash, but a product-rule mismatch).
4. Prefer screenshots or a walkthrough video so the issue is visible.

### Bug report template

```
I’m on [page/entry]. I did [step 1], then [step 2].
At [step], I see [error / no response / endless loading].
I expect [correct result]. It happens [always / sometimes]. Screenshot attached.
Please fix along this path; don’t change [parts that already work].
```

### Note

Describing reproduction is not the same as diagnosing root cause. You explain what you did; Su Xiaoqiang figures out why and how to fix it.

## Related docs

[Troubleshooting](/superun/tips-tricks/troubleshooting) · [Auto-fix](/superun/features/auto-fix)

## Original WeChat post

[Original WeChat post](https://mp.weixin.qq.com/s/8ArzKrQgMrvpX8svRnOKPQ)
