Troubleshooting
Common issues you may hit across the Polymarket dashboard, especially around Real Copy Trading.
Real Copy Trade setup
Low Gas Balance warning
What it says: “Wallet 0x... has X.XXXX POL. Fund with POL on Polygon (recommend ≥ 0.05).”
Cause: The signer EOA derived from your private key has less than 0.05 POL, which is the recommended minimum for the one-time approval transactions that run on your first trade.
Fix: Send POL to the wallet address shown in the warning, on Polygon mainnet. You can still submit the form with low gas; just fund before the first trade fires or the approval transactions will fail.
”Must be a 64-character hex string”
Cause: The private key field expects 64 hex characters, optionally prefixed with 0x. Common mistakes include trailing whitespace, a truncated paste, or pasting a seed phrase instead of a raw key.
Fix: Re-export the key from MetaMask (Account Details, Show Private Key) and paste it directly. Strip any spaces.
”Must be ≥ Position Size”
Cause: Max Exposure is set lower than Position Size. 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 Size.
Fix: Raise Max Exposure or lower Position Size until Max Exposure ≥ Position Size.
First trade issues
Approval transactions failed
What you’ll see: The first matching trade on a new automation writes a failed entry to the Activity log with a message like “USDC→CTFExchange approval failed: signer wallet has insufficient funds for gas.”
Cause: The signer EOA ran out of POL before the approval transactions confirmed.
Fix: Send POL to the signer wallet address on Polygon. The next matching trade automatically retries approvals. Approvals are idempotent, so you don’t need to manually re-trigger anything.
”Insufficient balance” on first buy
Cause: The funder address (or the EOA, if no funder is set) does not have enough USDC to cover the position size the automation is trying to open.
Fix: Send USDC to the funder address you configured. If you use Polymarket MetaMask, that is your proxy wallet address (visible on your Polymarket profile). If you use a standalone EOA, send to the EOA itself.
First trade took longer than subsequent trades
This is expected. The first trade on a new automation runs on-chain approval transactions before placing the order, which adds roughly 2 to 10 seconds of latency. Subsequent trades skip approvals.
Position anomalies
The position-manager runs every 5 minutes and reconciles on-chain positions against Airavat’s internal state (most positions are already settled within seconds by the event-driven settlement trigger). When the two disagree, the position is flagged with an anomaly badge on the Positions tab and the Position detail view.
| Anomaly | Badge color | Meaning | What to do |
|---|---|---|---|
appeared | Blue | On-chain shares exist for a market+outcome the automation never opened, typically pre-existing holdings from before the automation was created | Usually auto-dismissed as pre-existing. Safe to ignore. |
disappeared | Red | Airavat expected open shares, but on-chain shows zero | Check your Polymarket UI. If the position is truly gone (manual redemption, transfer, etc.), click Close on the Airavat position to reconcile. If it reappears, wait one more reconciliation cycle. |
shrunk | Yellow | On-chain shares are less than Airavat expected | Often ponder lag that self-corrects on the next cycle. If it persists past two cycles, contact support. |
grown | Yellow | On-chain shares exceed Airavat’s expected count | Usually a merge or partial redemption artifact. Self-corrects on reconciliation. |
Detection is two-strike. An anomaly must be detected on two consecutive reconciliation cycles before it is confirmed and surfaces a notification. If the discrepancy resolves in between, the pending flag clears silently.
Manual position close
The Close button appears on every open position row in Paper Copy Trade, Real Copy Trade, and Discretionary Trading automations.
Paper Copy Trade: the close is immediate. The position is marked closed at the current market price and PnL is realized instantly.
Real Copy Trade and Discretionary Trading: the Close button places a Fill-And-Kill sell order at the best available bid.
- The UI updates immediately and shows the position as
pendingwhile the order settles - Settlement typically confirms the close within seconds; position-manager runs every 5 minutes as a fallback
- You do not need to wait on the UI; the close is fire-and-forget
When it gets blocked:
- Position is already
closedorresolved - A sell is already in flight on the same position (wait for it to settle)
- Position has a
disappearedanomaly (closing is blocked until reconciliation resolves the state)
Caveats:
- Order fills at whatever bid is available. In illiquid markets the fill may be well below the mid price.
- The current UI closes the full position; partial close is not supported.
- If the order book is empty, the close retries briefly before failing. You can click Close again later.
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.
Notification bell not updating
The notification WebSocket uses the same reconnect policy (10 attempts, exponential backoff 2s to 30s). If your bell icon stops surfacing new notifications, refresh the page.
Getting help
- General questions: email support@airavat.xyz
When reporting an issue, include your automation ID (visible in the URL on the automation detail page) and the approximate time of the problem so we can find the relevant logs.