My transaction failed
A few common causes, ranked by frequency.
1. Insufficient gas (POL)
By far the most common. On-chain actions need a small amount of POL to pay network fees. If your wallet is out of POL, the transaction fails before it's even submitted.
Fix: top up POL. See Insufficient gas.
2. Insufficient USDC
Trying to place a buy order or withdraw more USDC than you actually have free. Note that funds locked in open orders and bonus credit under rollover don't count as free.
Fix: check the balance breakdown in your portfolio. Free up funds by cancelling an open order, or add money. See Reading your balance.
3. Wallet disconnected mid-flow
Wallet popups time out. If the signing prompt sat untouched for too long, the request expired.
Fix: retry the action; the wallet popup re-appears.
4. Market closed or in resolution
If you're trying to place an order on a market that just ended, the backend rejects it because the market is no longer active.
Fix: pick a different market, or sell an existing position you hold in the closed market once it resolves.
5. Network congestion or RPC instability
Polygon is usually fast, but during periods of network stress, RPC endpoints can be flaky. The transaction may have been broadcast but not confirmed; the wallet shows "failed" while the chain shows it as pending.
Fix: wait 1-2 minutes, then refresh the portfolio. If the transaction went through, the position appears. If not, retry.
6. The wallet itself is misbehaving
Some wallet extensions get into a bad state — pending requests queue up and new ones fail silently. If retries don't work:
- Refresh the page.
- Disconnect and reconnect the wallet.
- Restart the wallet extension.
When to email support
If a transaction failed, your wallet says it succeeded, and your portfolio doesn't reflect it after a few minutes — copy the transaction hash (from your wallet history or a block explorer) and open a support ticket. Include the hash; that's everything we need to look it up.
See Reporting a problem for a template.