> 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/chastye-oshibki-isa.md).

# ISA errors

Find where to investigate installation, sign-in, connection, key, bot, strategy or update problems.

## Check logs first

If the terminal opens, check general logs and, for a bot problem, that bot's logs. See [Logs](/en/isa-terminal/baza-znanii/logirovanie-v-isa.md).

## Installation fails

Check the Windows message and installer source. See [Installation problems](/en/isa-terminal/kak-ustanovit-algoterminal-isa.md) for SmartScreen, antivirus and administrator permissions.

## Stuck on the loading screen

Damaged program settings may cause this. Reinstallation normally keeps those settings, so the problem can return.

1. Close ISA Terminal completely.
2. Press **Win + R**, enter **%APPDATA%** and press **Enter**.
3. Find **isasoft**.
4. Keep it as a backup: rename it to **isasoft-backup**.
5. Start ISA Terminal again. It creates a fresh settings folder.

This often restores startup, but you will need to configure connections, bots, presets and other settings again. Old data remains in **isasoft-backup**.

Do not copy the old folder back in full, as the problem may return. If a clean launch does not help, keep the backup and contact support. Its logs are in **app-logs** and **logs**. Send only logs requested by support, not the entire backup folder.

## Cannot sign in

Check login/password, confirmed email, active access days, internet, and whether antivirus or the Windows firewall blocks the connection. Reset an incorrect password on the iSpecAlgo website.

## Exchange connection cannot be created

Read the save error. For keys, permissions and demo issues, see [Common API errors](/en/isa-terminal/birzhi-i-podklyucheniya/chastye-oshibki-api.md).

## Bot cannot be created

Check an enabled connection, selected ticker, strategy availability for this market, unique bot name, valid strategy settings and an unoccupied pair/side among all existing bots on the connection, including stopped ones. Futures-only strategies do not appear for Spot.

## Bot will not start

Possible causes: disabled or failed connection, no balance, another bot occupying the pair/side, unrelated futures position or orders, no exchange verification response, changed position mode, invalid settings, rejected orders or unsynchronized Windows time.

Check connection and balance, [position mode](/en/isa-terminal/birzhi-i-podklyucheniya/one-way-rezhim.md) and occupancy, then bot logs and the exact exchange error.

## Running, but no trades

This is not always an error. The strategy may await entry conditions, the current candle's close, a larger price move or a suitable signal. The required trading direction may be disabled, or the balance insufficient.

## Bot and exchange positions differ

Check position and active orders on the exchange, then bot logs. See [Position accounting and exchange checks](/en/isa-terminal/baza-znanii/kak-rabotaet-terminal-isa-i-ego-vzaimodeistvie-s-birzhei.md) for causes and actions.

## Position closed manually on the exchange

Follow the manual-close procedure in [Position accounting](/en/isa-terminal/baza-znanii/kak-rabotaet-terminal-isa-i-ego-vzaimodeistvie-s-birzhei.md) before restarting.

## “Position occupied”

Check all existing bots, including stopped ones. The pair or side may be reserved. See [Position modes](/en/isa-terminal/birzhi-i-podklyucheniya/one-way-rezhim.md) for allocation and conflicts. For unrelated exchange positions or orders, see the pre-start checks in [Position accounting](/en/isa-terminal/baza-znanii/kak-rabotaet-terminal-isa-i-ego-vzaimodeistvie-s-birzhei.md).

## No Telegram notifications

Check the bot token, chosen chat's Telegram ID, internet and selected event types. See [Telegram notifications](/en/isa-terminal/baza-znanii/kak-poluchat-uvedomleniya-v-telegram.md).

## Problems after updating

Restart the terminal and check logs. See [Updating ISA](/en/isa-terminal/kak-ustanovit-algoterminal-isa/kak-obnovit-isa.md) to return to another version.

## Contact support

If logs and guides do not resolve the issue, send an integrated [bug report](/en/isa-terminal/baza-znanii/kak-otpravit-bag-report.md).