Skip to content

Documentation

Troubleshooting

Why nothing is trading, what a WAIT or risk block means, lot size and margin, spread and pending-order refusals, notifications, licensing, broker compatibility, and restart behaviour.

Installer integrity failed

Re-download from your GoldMineBot portal. Do not bypass integrity checks. Contact support if a fresh official package still fails verification.

EA / cBot not trading

  • Confirm mode is not Advisory-only if you expected orders.
  • Confirm Algo Trading is ON (MT5) and account allows experts.
  • Confirm Kill Switch is not blocking.
  • Confirm Auto is explicitly armed after restart (arms do not restore).
  • Confirm license OS/platform matches the terminal you are using.

News protection always blocking

  • MT5: verify WebRequest allow-list and calendar data availability.
  • cTrader: expected fail-closed behavior when calendar data is unavailable.
  • Missing required safety data is intentional — GoldMineBot prefers WAIT over unsafe trades.

AI Gateway connection failed

  • Confirm the Gateway process is running on 127.0.0.1:8765.
  • Confirm http://127.0.0.1:8765 is allowed in MT5 WebRequest settings.
  • Confirm provider API key and Test Connection inside Settings.
  • Trading intelligence continues without AI; only explanations are unavailable.

Symbol mapping differences

Brokers may suffix symbols (e.g. XAUUSD.a). Use GoldMineBot symbol mapping guidance in the panel for custom names. Unmapped symbols stay fail-closed.

No trades are being opened

Work through this in order — most cases are one of the first four, and each of them is the product behaving as designed.

  1. Execution mode: Advisory is the default and never places orders. Assisted waits for your explicit PLACE.
  2. AUTO arming: arms reset OFF on every restart and are per style lane. Re-arm Normal or Scalping deliberately.
  3. Kill switch: if it is ON, no new trading activity is permitted.
  4. MT5 permissions: Algo Trading must be ON and the account must allow Expert Advisors.
  5. License scope: the license OS and platform must match the terminal you are running.
  6. Risk state: a loss limit, trade-count cap, exposure cap or consecutive-loss cooldown may already be blocking.
  7. Decision state: the current decision may simply be WAIT. Check the Analysis tab for the reason.

Everything says WAIT

WAIT is a complete, valid outcome, not a fault. It means at least one of confluence, regime, news, data quality or risk did not clear. The Analysis tab names the gate that did not pass.

  • A ranging or compressed regime legitimately produces long stretches of WAIT — the system is not designed to force a daily trade.
  • Extreme volatility and shock states are blocked on purpose.
  • Stale or missing market data produces WAIT rather than a guess.
  • Scalping is a separate lane; a WAIT in one style does not mean the other style agrees.

A signal was risk-blocked

A qualified setup can still be refused. The block reason is recorded, and the common ones are below.

Block reasonWhat to check
Daily or weekly loss limit reachedSettings → Risk. Trading resumes in the next period.
Maximum trades per day reachedSettings → Risk → maximum trades per day.
Maximum open trades or open risk reachedClose or let existing positions resolve; review the per-lane caps.
Consecutive-loss cooldown activeWait out the cooldown minutes, or review why the run of losses happened.
Portfolio or correlated exposure capProduct-level ceiling. Reduce concentration in the same theme.
News protection windowSettings → News, and the News tab for the event that is blocking.
Data quality failureCheck broker connection and symbol data. Fail-closed is intentional.

Invalid lot size

  • Your risk percentage and stop distance may produce a size below the symbol minimum lot — raise risk slightly or trade a symbol with a smaller minimum.
  • The computed size is rounded to the symbol volume step; a broker with a coarse step can reject a size that looks valid.
  • Check the symbol contract specification in MT5 for minimum lot, maximum lot and volume step.
  • Account currency and contract size affect the result — the same risk percentage gives different sizes on different symbols.

Insufficient margin

  • Free margin is checked before submission, so an order can be refused before it is sent.
  • Manual and foreign-EA positions consume the same account margin even though GoldMineBot does not manage them.
  • Account leverage and symbol margin requirements change what the same lot size costs.
  • Reduce risk percentage or the open-trade caps rather than topping up to force a trade through.

Entries refused on spread

  • The default maximum allowed spread is 80 points. Entries are refused while the live spread exceeds it.
  • Spreads widen at session rollover, around scheduled news, and on low-liquidity symbols — refusals there are the control working.
  • Raising the tolerance in Settings → Trading widens the conditions in which an order may be sent and increases execution-cost risk.
  • Entry deviation is a separate control: it governs how far price may move away from the planned entry.

Pending-order problems

  • A pending entry is not placed when the planned level sits inside your broker stop or freeze distance.
  • It is also not placed when the staleness bound is unavailable, or when price has already traded beyond the stop — the thesis is invalid by then.
  • GoldMineBot cancels its own pending orders once the thesis behind them is no longer valid. A disappearing order is usually this.
  • Where your broker does not support a specified expiry, validity is managed by GoldMineBot instead of by the broker.
  • Pending orders you placed yourself are never adopted or cancelled by GoldMineBot.

Notifications are not arriving

  • Lifecycle notifications are ON by default; in-product alerts are OFF by default (Settings → Display).
  • Mobile push is OFF by default and requires a MetaQuotes ID configured in your MT5 terminal.
  • Protection-event push is a separate toggle from lifecycle push.
  • Check that MT5 notifications are enabled in Tools → Options → Notifications as well as in GoldMineBot.

Licensing and activation problems

  • Entitlement is server-authoritative. Reinstalling, or moving to another computer, does not restart an expired trial.
  • One license covers one OS, one trading platform and one active device — check the scope matches the terminal you are in.
  • If the product locks and routes you to activation, the license or renewal state is the cause; Settings, History and Journal data are preserved.
  • Activate with the key from your portal dashboard. Keep keys private and never paste a full key into an unsolicited email thread.
  • During Trial, normal Product Updates are unavailable under current commercial policy.

Broker compatibility

  • Broker compatibility is not universal. GoldMineBot reads your symbol filling modes, stop and freeze distances, volume step and expiry support at runtime.
  • Where a broker supports neither stop nor stop-limit orders, the affected pending path is reported as not placeable rather than converted into a market chase.
  • Netting and hedging account types behave differently; position reconciliation accounts for both.
  • A canonical symbol profile means the architecture supports the symbol — not that your broker's variant of it is equally validated.

After an MT5 restart or reconnect

  • AUTO and REAL authorizations return to OFF by design. This is the single most common cause of "it stopped trading overnight".
  • Position state is rebuilt and uncertain claims are reconciled rather than resubmitted.
  • Do not manually resubmit an order whose result was reported as timeout or unknown — the claim is deliberately retained.
  • Management cannot act while the terminal is closed or disconnected.

Common configuration mistakes

  • Expecting orders while execution mode is still Advisory.
  • Expecting AUTO to resume by itself after a restart.
  • Running more than one GoldMineBot instance on the same chart symbol instead of one per symbol.
  • Raising risk percentage before watching the system behave on DEMO.
  • Assuming a Clean Chart has disabled analysis — chart layers are presentation only.
  • Assuming staged targets are active; each position is managed to a single take-profit target.
  • Treating a canonical symbol profile, or a research readiness label, as validated performance.

Get help

Use Contact with account email, OS, platform (MT5/cTrader), product version, and a short description. Do not send broker passwords or full license keys in unsolicited mail threads.