Echo Debugging

Troubleshooting common issues with Echo automated trade execution for scalping and swing signals.

If Echo is not executing trades or shows an error status, this guide covers the most common issues and how to resolve them.

Checking Echo Status

The first step when something seems wrong is to verify Echo's connection status in the Discord setup channel. Look for the status indicator:

  • Green / Active -- Echo is connected and ready to execute signals
  • Yellow / Warning -- Echo is connected but encountered a recent issue
  • Red / Inactive -- Echo cannot reach your exchange account

Common Issues

API Key Is Invalid or Expired

Symptoms: Echo shows inactive status immediately after setup, or stops working after a period of normal operation.

Causes:

  • The API key was deleted or regenerated on the exchange
  • The API key expired (some exchanges set expiration dates)
  • IP whitelist restrictions are blocking Echo's servers

Fix:

  1. Log into your exchange and check that the API key still exists and is active
  2. If the key has expired, generate a new one and update your Echo configuration
  3. If your exchange enforces IP whitelisting, make sure Echo's IP addresses are permitted (check the AlgoAlpha Discord for the current list)

Insufficient Balance

Symptoms: Echo is active but trades are not being placed, or only some trades execute.

Causes:

  • Your account balance is below the minimum order size for the asset
  • Funds are locked in open positions or pending orders

Fix:

  1. Check your available balance on the exchange
  2. Ensure you have enough free USDT to cover the configured position size
  3. Close any stale pending orders that may be holding margin

Wrong API Permissions

Symptoms: Echo shows an error related to permissions or authorization.

Causes:

  • The API key does not have futures trading enabled (for scalping)
  • The API key does not have spot trading enabled (for swing)

Fix:

  1. Go to your exchange's API management page
  2. Edit the key and enable the required trading permission
  3. Save and wait a few minutes for the change to propagate
  4. Restart Echo by deactivating and reactivating in Discord

Manual Trades Interfering

Symptoms: Positions are closed unexpectedly, or the portfolio does not match the signal allocation after rebalance.

Causes:

  • You placed manual trades on the same account Echo is managing
  • The swing rebalance at 0030 UTC exited positions it did not recognise

Fix:

  • Use a dedicated exchange account (or sub-account) exclusively for Echo
  • Do not open, close, or modify positions manually on the Echo-connected account

Exchange Maintenance or Downtime

Symptoms: Trades are missed during a specific time window, but Echo works normally otherwise.

Causes:

  • The exchange was undergoing scheduled or unscheduled maintenance
  • API rate limits were temporarily exceeded

Fix:

  • Check the exchange's status page for recent incidents
  • Missed signals during downtime cannot be retroactively executed -- monitor your positions after maintenance ends and adjust manually if needed

Echo Not Responding to New Signals

Symptoms: New signals appear in Discord but Echo does not place trades.

Causes:

  • Echo may have been deactivated
  • A configuration change may have broken the connection
  • The exchange may be rejecting orders due to risk limits

Fix:

  1. Verify Echo's status indicator is green/active
  2. Deactivate and reactivate Echo to force a fresh connection
  3. Check your exchange for any risk control notifications or restrictions

General Debugging Steps

If none of the specific issues above apply, follow these general steps:

  1. Verify status -- confirm Echo shows active/green in the Discord setup channel
  2. Test the API -- deactivate Echo, re-enter your API credentials, and reactivate
  3. Check balance -- ensure sufficient free USDT in the correct account type (futures for scalping, spot for swing)
  4. Check permissions -- confirm the API key has the right trading permission enabled
  5. Review exchange -- look for any notifications, restrictions, or maintenance alerts on your exchange
  6. Ask in Discord -- the AlgoAlpha support team and community members can help troubleshoot in the support channels

Getting Further Help

If you have tried the steps above and Echo is still not working:

  • Post in the #support channel on the AlgoAlpha Discord with your exchange name, the error message or behaviour you see, and the steps you have already tried
  • Email support@algoalpha.io for direct assistance (1-2 business day response)
⌘K