Troubleshooting

Common situations and what they mean. Many "problems" are GRIDer working as designed to keep you safe.

Setup & connection

I installed GRIDer but can't start a grid. You likely haven't finished instance setup. Confirm your licence is active, exchange access is configured, balances can be read, and order permissions are enabled.

The licence check fails. Check that your licence is active, the server clock is correct, and the instance can reach the licence endpoint if your plan requires online validation. A temporary validation failure should use the product's grace period and must not close a running grid; monitor the position and contact technical support if the issue persists.

The exchange API connection fails. Recheck the API key or agent wallet, permissions, IP allowlists and expiry. Make sure the key has trading permissions but no withdrawal permission.

I'm prompted to renew trading access. Some exchange approvals expire. Renew the venue-specific trading access so your running grids can keep trading.

Starting a grid

The grid won't start — "insufficient balance".

• Perps: you need funds in your perps (USDC) balance.
• Spot: you need enough spot USDC for the initial buy plus the first buy level. No order is placed if there isn't. Check the Balance card.

A validation error blocks me. GRIDer validates inputs before starting. Common ones:

• Stop-loss on the wrong side — LONG: below the lower limit; SHORT: above the upper.
• Close Grid Price on the wrong side — LONG: above the upper limit; SHORT: below the lower.
• Initial entry price outside the range — it must sit inside the grid range.
• Investment exceeds capital x leverage — lower the size or raise leverage carefully.

"There are active positions on this token." Close existing positions on that symbol before starting a grid on it, so the grid starts from a clean state.

A running grid

My grid shows "Pending entry" and isn't trading. You set an initial entry price, so the grid is waiting for that first limit order to fill before placing the rest. It'll proceed once filled. If it never fills, price hasn't reached your entry level — adjust or cancel and restart at market. See How a grid works.

My grid is "paused — margin/balance".

• Perps: other positions are using your margin, so an order was rejected. The grid pauses and resumes automatically when margin frees up. Add funds or reduce other positions to speed it up.
• Spot: not enough USDC (for buys) or tokens (for sells) at the moment. If it stays paused over 24h, consider adding funds or closing it.

My grid stopped on its own. GRIDer tries to maintain and recover grids safely, but if it can't continue with confidence (no position to rebuild from, price outside the range, insufficient margin/balance, or the instance was offline too long), it stops the grid by design rather than open a fresh position on your behalf. Review the position on the exchange and restart the grid manually if you still want it. See How a grid works.

My server restarted. Restart the GRIDer service and check the grid status. GRIDer attempts to reconcile real exchange positions and orders before resuming. If it cannot rebuild safely, it will stop the grid and ask you to review.

Closing

I got an urgent "close alert". A grid closed but couldn't fully flatten the position (usually extreme illiquidity during a market close). GRIDer surfaces this instead of hiding it. Finish the close manually on the exchange — close the residual position there. See Risk and range breakouts.

My PNL in history differs from what I expected. The recorded PNL is position PnL + closed PnL - exchange fees + funding, the same figure shown live in the panel. If it surprises you, open the breakdown while a grid runs to see each component. Funding in particular can be a quiet tailwind or headwind. See Costs, fees and funding.

Display

Prices or levels look wrong for this token. Some tokens use mixed casing (e.g. kPEPE) and many decimals; GRIDer formats by the exchange's own precision. If something still looks off, reload — and report it on Discord.

Still need help?

Ask on Discord or X. To capture your instance's logs for a ticket, see Logs & support. For anything touching your funds, remember GRIDer should never need withdrawal permission or your seed phrase.