DaneTrades Cloud runs the copier infrastructure for you. Do not diagnose Cloud delays by checking a personal PC, local terminal load or customer-managed Windows VPS.
Measure the actual event
Open Trade activity and compare the source event, receiver action and result rather than relying only on broker-history timestamps.
Use one affected event and its public reference ID.
Copying appears delayed
Possible causes include:
- the receiver platform responding slowly;
- a fast-moving or thin market;
- temporary receiver connection trouble;
- many source changes arriving close together;
- platform rate pressure;
- a symbol or account becoming unavailable during the action.
Retest with one small trade on a liquid, mapped symbol during normal market hours.
Duplicate ignored
Duplicate ignored is usually protective behaviour, not a request to resend the trade.
It means DaneTrades recognised the action as already handled and did not create another receiver order.
If the receiver still has an unexpected duplicate position, check whether:
- two separate copiers target the same receiver;
- two different sources generated similar trades;
- a Telegram provider sent repeated signal messages;
- the extra trade was placed manually or by another system.
Failed to send or timeout
A timeout means the receiver platform did not provide a usable result within the expected request window. It does not automatically prove that the broker performed no action.
Do not repeatedly recreate the same connection or trade while an operation may still be completing.
Use Trade activity and the current receiver position before deciding what happened.
Requotes, off quotes and price changes
These are receiver-platform outcomes commonly associated with:
- fast markets;
- news events;
- rollover;
- thin trading sessions;
- stale or rapidly changing prices.
Retest during normal liquid conditions before changing unrelated copier settings.
Repeated problem on one platform
If the same platform repeatedly shows delays or timeouts while other platforms are healthy, continue to support with several public reference IDs from a narrow time window.
Do not include passwords, API secrets, access tokens or raw credentials.
When to continue to support
Continue to support when:
- the issue repeats on clean, small tests;
- the account and copier show ready states;
- the event outcome does not explain the delay;
- or the receiver result appears inconsistent with Trade activity.
Provide two or three representative reference IDs, not an unbounded history.