⚠️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.
Installation fails
Check the Windows message and installer source. See Installation problems 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.
Close ISA Terminal completely.
Press Win + R, enter %APPDATA% and press Enter.
Find isasoft.
Keep it as a backup: rename it to isasoft-backup.
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.
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 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 for causes and actions.
Position closed manually on the exchange
Follow the manual-close procedure in Position accounting before restarting.
“Position occupied”
Check all existing bots, including stopped ones. The pair or side may be reserved. See Position modes for allocation and conflicts. For unrelated exchange positions or orders, see the pre-start checks in Position accounting.
No Telegram notifications
Check the bot token, chosen chat's Telegram ID, internet and selected event types. See Telegram notifications.
Problems after updating
Restart the terminal and check logs. See Updating ISA to return to another version.
Contact support
If logs and guides do not resolve the issue, send an integrated bug report.
Last updated