DaneTrades Cloud

Trades Not Copying in DaneTrades Cloud

This guide is for DaneTrades Cloud Copier. It does not cover Local Copier install, EA, or device-slot workflows.

DaneTrades Cloud — web-managed copying for supported trading platforms. Telegram is a signal source only.

This guide is for DaneTrades Cloud. Do not use EA, AutoTrading, WebRequest, personal-PC or customer-managed VPS checks for this product.

Start with the affected event

Open Trade activity and find the source trade or attempted receiver action.

The displayed outcome tells you which area to check:

  • Not copied: filter means a current copier rule intentionally blocked it.
  • Not copied: risk/sizing means the receiver size could not be produced safely.
  • Not copied: missing symbol map means the source symbol is not mapped to a receiver symbol.
  • Not copied: billing/licence means billing access or account capacity prevented copying.
  • Failed to send means DaneTrades did not record a usable successful receiver response.
  • Rejected by broker means the receiver platform returned a clear rejection.
  • Duplicate ignored means DaneTrades recognised the action as already handled and did not send another order.

1. Check both trading accounts

Open Trading Accounts.

Both the source and receiver should be ready for copying. If either account shows Connecting, Connection failed, Paused or Billing blocked, resolve that status first.

A broker account can authenticate successfully while its symbol list is still loading. Wait until the account is fully ready before testing a copier.

2. Check the copier

Open Copiers and select the affected copier.

Confirm:

  • the correct source and receiver are selected;
  • copying is active rather than paused;
  • the copier is not showing Setup needed or Mapping needed;
  • safe mode is not blocking new opens;
  • include and exclude symbol lists permit the source symbol;
  • Copy sells is enabled when the missing source action was a sell.

The current Cloud editor does not have a separate buy-copy toggle.

3. Check symbol mapping

Confirm the exact source symbol maps to the exact receiver symbol.

Examples of broker naming differences include:

  • GOLD and XAUUSD;
  • NAS100 and USTEC;
  • EURUSD and a suffixed symbol such as EURUSDm.

Do not assume a similar-looking symbol is the same instrument. Confirm it in the receiver platform.

4. Check sizing and margin

For diagnosis, use one small trade and a simple sizing mode.

Check:

  • receiver minimum and maximum volume;
  • receiver volume step;
  • available free margin;
  • receiver leverage and contract size;
  • whether a risk-percent trade has a valid stop loss.

Risk-percent sizing needs a usable stop loss. DaneTrades does not invent a risk distance when the source trade has none.

5. Check the broker result

If Trade activity says Rejected by broker, expand the event and use the displayed reason.

Common broker-side causes include:

  • invalid volume;
  • insufficient margin;
  • market closed;
  • symbol unavailable;
  • stop levels too close to price;
  • account or instrument restrictions.

Correct the specific cause rather than repeatedly reconnecting unrelated accounts.

If Trade activity says Failed to send, do not assume the broker accepted or rejected the action. Check the broker account before any retry that could create duplicate exposure.

Retest cleanly

After making one change:

  1. use one source account and one receiver;
  2. use one mapped, liquid symbol;
  3. place one tiny test trade;
  4. check the new Trade activity event;
  5. avoid changing several settings at once.

When to continue to support

Continue to support when:

  • both accounts are ready;
  • the copier is active and correctly configured;
  • the symbol is mapped;
  • the receiver can accept the intended size;
  • and the latest event still has no clear customer action or repeatedly fails.

Provide the Trade activity reference ID, expected result and actual result. The assistant can include the relevant Cloud context in the handoff after you confirm submission.