This guide is for DaneTrades Cloud.
Trade activity shows the customer-facing result of recent copy actions. Expand an item to see its details and public reference ID.
Copied
The receiver platform returned a successful response for the copied action.
Check the receiver account if you need to compare the resulting broker position or order details.
Not copied: filter
A current copier rule intentionally blocked the action before it was sent.
Check:
- include and exclude symbol lists;
- Copy sells when the source action was a sell;
- safe mode;
- the current customer-safe filter reason shown in the activity detail.
Change only the rule you intend to change, then retest once.
Not copied: risk/sizing
The action was blocked before send because the requested receiver size or risk calculation was not usable.
Common causes include:
- risk-percent sizing without a usable stop loss;
- an invalid calculated size;
- receiver minimum, maximum or lot-step constraints;
- insufficient account information for the chosen sizing mode.
Next step: test with a small fixed lot when appropriate to separate sizing configuration from other restrictions.
Not copied: missing symbol map
DaneTrades could not resolve the source symbol to a committed receiver symbol.
Next step: open the copier, update Symbol Mapping, save and retest that symbol.
Not copied: billing/licence
The workspace billing state or paid account capacity blocked the action.
Next step: open Billing, restore the required paid capacity or billing state and test again after the app updates.
Duplicate ignored
DaneTrades recognised the action as a duplicate and did not send it again.
This is protective behaviour. If you believe two genuinely different actions were treated as one, keep the public reference ID and continue to support.
Failed to send
DaneTrades did not record a usable successful receiver response for the send attempt.
Do not assume the receiver accepted or rejected the action.
Next steps:
- Check the receiver broker account directly before any retry that could create duplicate exposure.
- Check the receiver account state in DaneTrades.
- Review the customer-safe activity detail.
- Continue to support when the result repeats or remains unclear.
Rejected by broker
The receiver platform clearly rejected the action.
The activity detail should show a customer-safe reason where available. Common causes include invalid volume, insufficient margin, invalid protective levels, market state or broker restrictions.
Next step: correct the shown cause. Reconnecting alone will not fix a clear broker rejection.
Public reference ID
Each activity item has a support-friendly reference ID. It lets support find the exact action without asking for credentials or a large log export.
Provide the reference ID when:
- the same failure repeats;
- the displayed reason does not match what happened;
- a duplicate was ignored incorrectly;
- a copied result appears inconsistent;
- Support Assistant asks you to continue to support.
What Trade activity does not guarantee
Trade activity records DaneTrades' customer-facing copy outcome. It does not guarantee identical price, slippage, margin behaviour or broker state between different accounts and platforms.
The customer-facing outcome list is limited to the eight results described above. Internal worker, queue, heartbeat, proof or review states are not customer outcomes.