Best Traders to Copy

Copy interruptions and recovery records

Keep missed, duplicated, delayed and unresolved actions in the record instead of letting a resumed connection erase the gap.

Added 15 October 2026

Name the interruption interval

A connection status and a complete execution population are different records. Preserve when the interruption was observed, which service owned the signal path and what source resolution is available. A resumed connection does not prove every earlier action was received or copied. The publication does not monitor a live copier or create a workstation fallback. Its tools run on supplied records. An actual copying service should be assessed under its own documented hosting and recovery process. Do not substitute an operator's personal computer as a production dependency or infer recovery success from a green indicator alone.

Separate publication, receipt and execution

The leader may act while the follower receives nothing, receives a delayed instruction or has an execution rejected. These stages need distinct identities and clocks. A source trade cannot supply a missing follower fill. A message receipt does not prove order acceptance. The coverage ledger therefore permits an unresolved fill rather than forcing it to zero or the intended amount. It does not reconstruct the delivery chain. An actual investigation should preserve raw events, source times and the authoritative account record. A later profitable observation cannot fill a missing acknowledgment in the earlier interval.

Duplicate events need ownership

A retry can create several messages for one underlying action. Do not count duplicate deliveries as independent source trades or silently add their quantities. Preserve message identities and the original event relationship. The public ledger rejects duplicate row identities, but it cannot detect semantic duplicates given different IDs. That remains a source reconciliation task. A paired price journal similarly cannot decide that two supplied rows overlap the same economic slice. Keep the population and pairing convention explicit. Precision in the arithmetic does not replace evidence of which original position or action owns a quantity.

Distinguish catch-up from new activity

A recovered service may process delayed actions differently from new ones. The applicable product documentation and actual account logs define what happened. This guide does not assume a universal catch-up policy or invent a replayed fill. Record the transition event, inventory before and after and any administrative decisions. A source position already closed before recovery may create a different question from a current open position. The publication's row calculations do not simulate this lifecycle. A detailed discrepancy packet should keep the unresolved sequence rather than use whichever interpretation makes both account paths look identical.

An authored recovery contrast

A fictional interval can contain source L1, missed receipt R1 and an unresolved follower row Q4. Mark Q4 unresolved until an authoritative observation is supplied. One controlled variant records a partial fill; another records skipped zero. They are different scenarios, not proof that either recovery occurred. The known-subset ratio changes when the missing observation is resolved. Preserve the earlier snapshot and its scope. This demonstrates why a connection-restored event cannot retroactively certify execution coverage or erase an unresolved action from the population.

Close with the known gap

The practical conclusion names the interruption window, observed stages, duplicate relationships and remaining unknowns. A platform status can support its own observation without establishing account equivalence. Broker reconciliation and strategy validation stay null in the new tools. No local production monitor, replay engine or order sender is introduced. The buyer can use the source-bounded packet to ask which recovery records exist and which account events they establish. That adds useful depth without inventing a delivery success rate, a provider outage history or a favorable follower result from incomplete records.

Primary references

Source and follower records