Troubleshooting

Common issues you may hit across the Hyperliquid dashboard.

Pod configuration

Paper pod records no trades

Cause: The filter is starving. Criteria that are too tight can match near-zero traders, or the trade-size minimum can skip everything.

Fix: Open the filter in the builder and read the live estimate banner at the bottom — it refreshes automatically and shows how many active traders and assets match. If the matched trader population is tiny, loosen a criterion (lower Sharpe or Trader Score minimums, drop the Profit Factor constraint, or lower the Trade Size minimum). See Quick Start: Paper Trading for target trade-flow ranges.

Email pod has no email address / throttle

Cause: Email pods require both an email address and a throttle config.

Fix: Add the email address and set a throttle cap (per hour or per day).

Manual position close

The Close button appears on every open position row in copy-trade pods. The close is immediate: the position is marked closed at the current market price and PnL is realized.

When it’s unavailable:

• Email pods don’t hold positions — there’s nothing to close. Close only appears on copy-trade pods.
• Position is already closed.

Caveats:

• The close uses the current market price. In thin perps that price can move quickly.
• The close is full-position; partial close is not supported from the dashboard.

Live data and WebSocket

”Live updates disabled” / Activity feed stops updating

Cause: The WebSocket gave up after repeated reconnection failures.

Fix: Refresh the page to restart the connection. If it happens repeatedly, this usually points to a network issue (corporate firewall, VPN) blocking WebSocket traffic.

Stale prices on asset or trader pages

Cause: Price/position data is fetched from Hyperliquid on a cadence and can lag the exchange by seconds.

Fix: Refresh the page. If the issue persists, check your network.

Getting help

• General questions: email support@airavat.xyz

When reporting an issue, include your pod ID (visible in the URL on the pod detail page) and the approximate time of the problem so we can find the relevant logs.