> For the complete documentation index, see [llms.txt](https://khalil-lab.gitbook.io/evolver/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://khalil-lab.gitbook.io/evolver/contributing/reporting-a-bug-hardware-failure.md).

# Reporting a Bug / Hardware Failure

## Is it a bug / failure?

Examples of things that aren't considered bugs / hardware failures:

* Can't figure out how to do something
* Having issues installing software or setting up eVOLVER
* My experiment failed
* I want the eVOLVER to do something different (If you have a new feature request please post on the [forums](https://www.evolver.bio/))

If your issue falls into one of these categories, please use the [troubleshooting documentation](/evolver/troubleshooting/troubleshooting-overview.md) or ask on the forums

## Before reporting a new issue

1. Carefully read the documentation for the affected part.
2. Use the [troubleshooting ](/evolver/troubleshooting/troubleshooting-overview.md)documentation
3. Software - Make sure you are running the latest versions of the GUI and DPU
4. Try to narrow it down to reproducible steps. If we can reproduce it, we will be able to fix the issue faster.
5. Check the known issues pages for [hardware](/evolver/hardware/known-issues.md) and [software](/evolver/software/known-issues.md), also check issues for software on GitHub
   1. Should your bug be described there, comment on the issue that you are also experiencing it
   2. Add additional information if you can
6. Search the [forums](https://www.evolver.bio/) using a few different search terms.
7. If you got this far, then report an issue.

## Reporting a new issue

1. Make an issue on the relevant [software](/evolver/software/overview-of-software-architecture.md) GitHub or the [hardware ](https://github.com/FYNCH-BIO/hardware)GitHub
2. Characterize the problem in a [forum post](/evolver/contributing/documentation/making-a-forum-post.md)
3. If this bug / failure is detrimental to you, please consider developing a solution


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://khalil-lab.gitbook.io/evolver/contributing/reporting-a-bug-hardware-failure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.