Common Errors

Wallet has no bot_type

Cause: An execution wallet entry in the database does not have a bot type assigned. This can happen when:

• The wallet was created before the bot type field was introduced (legacy data)
• An incomplete form submission was stored without a bot type

Remedy:

1. Navigate to Dashboard > Futures Wallets
2. Identify the execution wallet without a bot type
3. Delete the wallet entry using the remove action
4. Re-create the wallet using the Add Wallet form, this time selecting the correct bot type (Bastion, Vanguard, or Orbit)
5. If the wallet entry appears to be legacy data you cannot delete via the dashboard, contact Aegis support — bot type cannot be edited after creation

See Futures Wallets for the full Add Wallet form field reference.

---

Insufficient margin

Cause: Your exchange futures account balance has dropped below the margin level required to open or maintain the hedge position.

Remedy:

1. Log in to your exchange account (Binance or HyperLiquid)
2. Deposit additional funds into your futures/trading account
3. Alternatively, reduce position size or leverage in your Aegis strategy to lower the required margin
4. Check Leverage and Margin for the margin model used by Aegis

---

API key permission denied

Cause: The exchange API key stored in Aegis is missing one or more required trading permissions, or has exceeded permissions (e.g., withdrawal enabled).

Remedy:

1. Log in to your exchange account and review the API key permissions
2. Compare them against the permission matrix in API Keys Overview
3. Create a new API key with the correct permissions
4. Remove the existing execution wallet entry in Dashboard > Futures Wallets
5. Re-add the execution wallet with the new API key credentials

See Binance API Keys and HyperLiquid API Keys for step-by-step key creation guides with the required permission settings.