Troubleshooting
Common issues you may hit across the Polymarket dashboard.
Pod configuration
”Must be ≥ Position Sizing”
Cause: Max Exposure is set lower than Position Sizing. Max Exposure is the cap on total exposure per market+outcome as a percent of effective capital, so it cannot be smaller than the per-trade Position Sizing. (This only applies when Scale-up is enabled, the only time Max Exposure takes effect.)
Fix: Raise Max Exposure or lower Position Sizing until Max Exposure ≥ Position Sizing.
Paper pod records no trades
Cause: The filter is starving. Criteria that are too tight can match zero traders, or the trade-size minimum can skip everything.
Fix: Open the filter and click Estimate coverage. If the matched 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.
Manual position close
The Close button appears on every open position row in Paper Copy Trade pods.
The close is immediate: the position is marked closed at the current market price and simulated PnL is realized instantly. A Close All button at the top of the Open Positions tab closes every open position sequentially (confirmation required).
When it gets blocked:
- Position is already
closedorresolved
Caveats:
- The close uses the current market price. In thin markets that price can move quickly.
- The current UI closes the full position; partial close is not supported.
Live data and WebSocket
Stale prices on market detail pages
Prices on the market detail page update via WebSocket.
Fix: Refresh the page. If the issue persists, check your network.
”Live updates disabled” on market detail
After 10 failed reconnection attempts (with exponential backoff between each), the WebSocket gives up and live updates are disabled entirely for the session.
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.
Activity tab not updating
The Activity Tab WebSocket reconnects automatically (up to 20 attempts, exponential backoff 2s to 30s). If the Activity Tab stops showing new entries or the badge count stops updating, refresh the page.
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.