Leg Error State
A leg enters an error state when an order execution attempt at the exchange fails. Common reasons:
- Order rejected by the exchange — insufficient margin, invalid order size, or the exchange rejected the order for an unspecified reason
- Exchange connectivity failure — the exchange API was unreachable when the bot tried to place or close the order
- API key permission issue — the API key does not have Futures Trading permission for the required order type
The leg FSM moves to the error state and stops trying to execute until the condition is resolved or the bot recovers.
Remedy
Section titled “Remedy”Step 1: Check the exchange status
Section titled “Step 1: Check the exchange status”Verify the exchange is operational. If the exchange experienced an outage, see Exchange Downtime.
Step 2: Check API key trading permissions
Section titled “Step 2: Check API key trading permissions”Verify the API key has Futures Trading permission enabled. See API Key Rejected for the full diagnostic.
Step 3: Retry via the dashboard
Section titled “Step 3: Retry via the dashboard”- In Dashboard > Pools View, locate the strategy with the leg in error state
- Use the strategy controls to retry or reset the leg (if the retry option is available in the current dashboard version)
Step 4: Wait for auto-recovery
Section titled “Step 4: Wait for auto-recovery”If the root cause (exchange downtime, temporary API issue) has resolved, the bot will attempt to recover the leg on the next monitoring cycle without user action.
Step 5: Contact support
Section titled “Step 5: Contact support”If the leg remains in error state after the exchange is confirmed operational and the API key permissions are correct, contact Aegis support. Include the error details from the dashboard activity log.