# Issues and signals

> How Semaloop surfaces UI/UX problems it notices while testing — signals, the issues they combine into, and how to manage them.

Rendered version: https://docs.semaloop.com/issues-and-signals/

While running your tests, Semaloop notices problems beyond the goal you asked it to check. Each observation is a signal, and related signals combine into issues you can review, resolve or archive.

* [**Understanding signals**](/issues-and-signals/understanding-signals/) — How Semaloop surfaces UI/UX problems it observes while running your tests.
* [**Understanding issues**](/issues-and-signals/understanding-issues/) — How individual signals combine into issues you can review.
* [**Managing issues**](/issues-and-signals/managing-issues/) — The Open, Resolved, and Archived states an issue can be in.
* [**Leaving feedback**](/issues-and-signals/leaving-feedback/) — Tell Semaloop when a signal or issue was helpful, or wasn't.

## Related

- Index of every Semaloop docs page: https://docs.semaloop.com/llms.txt
- All Semaloop docs in one file: https://docs.semaloop.com/llms-full.txt
