Bot isn't trading — checklist

Go to /app/settings → Trading credentials card. The master switch and the v6.4 + v7 per-strategy switches all need to be ON. If any is OFF, signals for that scope are being skipped.

If you recently clicked 'Close all + disable', the per-strategy toggle is OFF and the bot has been told to stop opening new positions. Toggle back on to resume.

v6.4 and v7 enforce max 1 position per market per strategy. If ETH is already open on v6.4, v6.4 won't open another ETH position regardless of signals. Check /app for current open positions.

Cross-strategy: only one strategy can hold a given market at a time (conflictGuard). If v6.4 is holding ETH and v7 wants to open ETH, v7 is blocked until v6.4 closes.

The regime gate (ADX > 25 + ETH directional index) is the main filter. It can stay 'closed' for weeks in choppy/sideways markets — that's by design, the strategy avoids low-confidence entries.

Look at the /app/performance or /backtest page: are there historical periods of similar silence? If yes, this is normal. If no, something else is wrong.

After a stop-loss, the bot enforces an SL cooldown (15-30 minutes, depending on strategy) to avoid re-entering immediately on the same setup that just failed.

After any signal, an 18h cooldown applies on that coin. Check the bot logs (or in-app log viewer if you have admin access) for 'cooldown' lines.

If your trading key was revoked, the bot's signing attempts will fail. Check pm2 logs for authenticator errors. Re-run the wizard if needed.

If the bot host's .env is missing one of DYDX_OWNER_ADDRESS / DYDX_API_PRIVATE_KEY / DYDX_AUTHENTICATOR_ID, the bot is falling back to mnemonic signing (or failing entirely).

Check https://status.dydx.trade or the dYdX Twitter. During chain outages, the bot can't place new orders. It also can't cancel existing ones — but TP/SL set on-chain still fire from the chain itself.