Help Center Category

Fix copying problems by symptom, error, or workflow

Start here when trades are not copying, sizes look wrong, stops or take profits are missing, execution is delayed, or logs show broker and platform errors. These guides are updated for the current web-managed, local-runtime DaneTrades model.

  • Built around current app labels like Copiers, Logs, and Copy Health
  • Useful for both direct account copying and supported signal workflows
  • Structured for symptom searches and long-tail error queries

Recommended order

Start in this order for the fastest diagnosis

  1. Trades not copying. Start there first if nothing is landing on the receiver.
  2. Logs and Copy Health. Use the exact log wording to jump to the most relevant guide.
  3. Symbol and sizing issues. These are the most common causes after connection state.
  4. Stops, take profits, and close events. Use these when entries copy but follow-up actions fail.
  5. Execution and platform issues. Use these for delays, requotes, timeouts, and MetaTrader-specific problems.

Current symptom and error guides

Use the guide that matches the closest symptom or log wording you are seeing.

Start here

Trades not copying

The main decision-tree guide for enabled connections, account state, logs, symbol mapping, and sizing checks.

Symbols

Symbol not found or wrong symbol traded

Fix missing symbols, suffix or prefix mismatches, and auto-mapped symbols that land on the wrong instrument.

Sizing

Wrong lot size, invalid volume, or insufficient margin

Understand lot calculation, broker minimums, volume step rules, and margin rejections.

Stops and targets

SL or TP missing, rejected, or not copying

Handle invalid stops, blocked modify events, and the common case where the trade opens but SL or TP does not stick.

Exit behavior

Positions not closing or partial closes not copying

Fix close-event problems, partial-close mismatches, and receivers that stay open after the master exits.

Execution quality

Copying delayed, duplicates, requotes, or timeout errors

Work through duplicate events, latency, platform load, and fast-market execution problems.

Platform state

Market closed, no prices, or trade context busy

Fix MetaTrader and broker state problems that stop execution even when the connection itself is fine.