> For the complete documentation index, see [llms.txt](https://docs.ispecalgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ispecalgo.com/en/isa-terminal/baza-znanii/kak-otpravit-bag-report.md).

# Bug reports

A bug report is an in-app form for telling support about a problem: unexpected behavior, a crash, a bot that will not start, connection or interface errors, or problems after an update.

Describe the problem in your own words. The terminal attaches diagnostic data automatically. This does not replace the support chat, but is a convenient way to send the description with the required files.

## Automatic attachments

You do not have to find these manually:

| Data                                   | Purpose                                    |
| -------------------------------------- | ------------------------------------------ |
| Application logs for the last 24 hours | Reconstruct application events             |
| Bot logs for today and yesterday       | Investigate trading behavior errors        |
| Order history for the last 2 days      | Investigate trading situations             |
| Critical crash files, if present       | Find the cause of a crash                  |
| System information                     | Identify the affected computer environment |
| Recent terminal actions                | Reconstruct your steps                     |

Do not enter API keys, API Secret or passwords in the form. Secret keys are not deliberately included in the report. Logs may contain bot names, trading pairs and exchange error messages needed for diagnosis.

## Open and fill the form

Click the account icon at the top right. The panel shows your email and license status. Select **Bug report**.

| Field               | What to enter                                    | Limits                         |
| ------------------- | ------------------------------------------------ | ------------------------------ |
| Title               | Brief problem summary, e.g. “Bot will not start” | 3–30 characters                |
| Description         | Steps, actual result and expected result         | 10–1000 characters             |
| Occurrence          | Once, occasionally or always                     | Select an option               |
| Contact information | A working email or Telegram contact              | Use a reachable contact        |
| Screenshots         | Images showing the error or situation            | Up to 3 files, up to 2 MB each |

The description includes a template:

> **Steps:** what you clicked or changed.
>
> **Actual result:** what happened.
>
> **Expected result:** what should have happened.

For example:

> **Steps:** Created and enabled Bybit Spot; created a GRID bot on BTCUSDT, 5m; pressed Start in My bots.
>
> **Actual result:** The bot shows an error and places no orders.
>
> **Expected result:** The bot starts and begins operating.

## Send

Click **Send** and wait for the result. A success notification means support received the report for investigation.

If sending fails, check internet, restart ISA Terminal and try again. If it still fails, contact support manually with a text description.

## Help support investigate faster

Explain what you did, what happened and what you expected. For trading problems include exchange, Spot/Futures market, connection, strategy, bot name, ticker, timeframe and frequency of the issue. A screenshot is optional but often helpful.

Do not include passwords, API Secret, private keys or unnecessary personal data. “The bot does not work” is too vague. Better:

> Every time I start LONGER on Bybit Futures BTCUSDT, it enters an error state. I attached a screenshot and provided my Telegram contact.

## Common questions

**Is internet required?** Yes, reports are sent to the server.

**What is required to send one?** Sign in, keep the terminal running and connect it to the internet. Open the form from the account panel.

**Can I omit screenshots?** Yes, but they help when the screen shows an error or unusual behavior.

**Are passwords and keys sent?** Secret keys are not deliberately added. Diagnostic logs are attached. Do not type sensitive data into the description or show it in images.

**When will I get a reply?** Support replies to the email or Telegram you provided. Timing depends on workload and issue complexity.

**What if sending fails?** Check internet, restart, retry, then contact support manually if needed.

## Quick reference

**Account icon → Bug report → title (3–30 characters) → description (steps, actual, expected) → frequency → email/Telegram → optional screenshots (3 × 2 MB maximum) → Send**.