RPC Failures

RPC connection failed

Cause: The RPC node used to read on-chain state (pool prices, LP positions) is temporarily unreachable or rate-limited.

Aegis behavior: Aegis maintains a pool of RPC providers and automatically fails over to an alternative provider when the primary is unavailable. In most cases, RPC failures are transient and resolve without user intervention.

Remedy:

1. Wait and allow Aegis to retry automatically — the bot will resume normal operation once an available RPC provider responds
2. If the issue persists for more than a few minutes, check the Aegis status surface for any announced infrastructure events
3. Contact Aegis support if the bot shows sustained ERROR alerts or the pools view stops updating

Do not attempt to change or configure RPC providers in any configuration file. RPC provider management is handled by the Aegis infrastructure and is not a user-configurable setting.

---

Stale oracle

Cause: The on-chain price feed (oracle) for a supported pool has not been updated within the expected interval. This can occur during low-liquidity periods or chain-level congestion.

Aegis behavior: The bot pauses price-dependent operations and waits for the oracle to recover before acting on LP range trigger conditions.

Remedy:

1. Wait for the oracle price feed to recover — this is typically an on-chain condition that resolves automatically
2. Monitor the activity log in Dashboard > Analytics for oracle-related events
3. Check the Aegis status surface or contact support if the stale oracle condition persists beyond a few minutes