> For the complete documentation index, see [llms.txt](https://graphdex-1.gitbook.io/graphdex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://graphdex-1.gitbook.io/graphdex-docs/copy-trading/history.md).

# Copy History

**The История sub-tab — closed copies, with final P/L and the trade record that produced it.**

When a copy is stopped or all its open positions resolve, it moves out of Active Copy into **История** (History). This is where you read what actually happened.

## What History shows per row

* **Trader** — who you copied.
* **Period** — start and end dates of the copy route.
* **Trades** — count of trades mirrored during the route.
* **Final P/L** — realised result. Sum of every closed copied position.
* **Win rate (yours)** — wins ÷ trades for this specific copy.
* **Details** — drill-down to the full per-trade tape.
* **Re-Copy** — quick action to start a new copy with the same settings.

## Filters

The same category pills and timeframe toggles apply on History — narrow to copies of traders in one category, or look at all your closed routes over a long window.

## Reading the result

A negative Final P/L row tells you the copy lost money. A positive one tells you it made money. The interesting work is in **why**:

* **Big losses concentrated in one market** — trader caught one bad event. Could happen again.
* **Steady losses across many trades** — strategy didn't work in this window. Probably won't tomorrow either.
* **Big gains concentrated in one market** — you got lucky on their best call. Don't extrapolate.
* **Steady gains across many trades** — the trader's edge is real. Re-Copy with higher confidence.

The Win rate column is most useful for high-volume closed copies. Few-trade copies have wide variance and the percentage doesn't mean much.

## When to Re-Copy

* Final P/L is positive after meaningful sample.
* Per-trade details show consistency, not a single freak win.
* Trader is still active (check their Top board entry — if they have stopped trading, Re-Copy has nothing to mirror).

## When NOT to Re-Copy

* Final P/L is negative with no clear external explanation.
* Trader's categories drifted from yours.
* You stopped the original copy because the size was wrong — re-do the math first, then re-Copy.

{% hint style="info" %}
History is the audit log of your copying behaviour. It's worth reviewing periodically even when you have nothing active — patterns about your own copy decisions surface here.
{% endhint %}

## FAQs

<details>

<summary>Does History include cancelled copies (started then stopped before any trades)?</summary>

Yes, but with zero trades and zero P/L. They are useful only as a record that you considered and dismissed.

</details>

<details>

<summary>Can I export my copy history?</summary>

Export tooling is limited in the current build. You can read the table in-page and screenshot or copy values for record-keeping.

</details>

<details>

<summary>How long is data retained?</summary>

Indefinitely so far — closed copies show up regardless of how long ago they ran.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://graphdex-1.gitbook.io/graphdex-docs/copy-trading/history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.