# Feedback and Reporting Issues

Accurate reports are critical for node/miner/RPC stability.

## What to include in every report

* Environment: Docker or source build
* Config context: relevant `run/hydra.toml` fields (sanitize secrets)
* Exact command executed
* Full error output
* Time range of issue
* Node ID (if available)

## Required logs

### Docker

```bash
docker logs -f mazze-node
docker logs -f mazze-miner
```

### Source build

```bash
tail -n 300 run/logs/mazze-node.log
tail -n 300 run/logs/mazze-miner.log
```

## Useful diagnostic checks

```bash
./run/mazze-cli.sh status
./run/mazze-cli.sh summary
```

And RPC status call from [RPC Guide](/testnet/rpc.md).

## Where to report

Use the official Mazze support/community channels and include the full context above so issues can be reproduced quickly.


---

# Agent Instructions: 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:

```
GET https://docs.mazze.io/testnet/feedback-and-reporting-issues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.