Trace trades, orders and broker history

Choose the evidence and exact account#

Audit combines retained AMM strategy runs/trade events with a separately identified authoritative account ledger. Broker history retrieves provider-reported orders, fills and deals through its own history view. These sources have different retention and completeness. A historical list does not automatically reconstruct every event in an account.

Start with exact broker, account and Demo/Live environment. The same ticker on another account is not the same event stream. Audit has Audit Explorer and Audit Detail panels; restore a hidden panel through the item's add menu. Open two Audit items if you need independent filters and selections.

Find a run or trade in Audit Explorer#

1. Open Audit and choose All trades, Algos or Portfolios.
2. Use All trades for the event timeline, Algos to locate a strategy run, or Portfolios to work through a portfolio's runs.
3. Search by algorithm, run, session, symbol or trade ID. Apply the available event/status chips and account filter.
4. In the filter menu, choose Day (timeline) or Run, then AMM trade for All trades grouping. Choose the specific account instead of Any account when investigating shared symbols.
5. Select the run, trade or event to populate Audit Detail. Use Load older events when the timeline has more retained events; the visible list is not necessarily the complete history.
6. Use Refresh now (R) for a fresh read. A failed refresh offers Retry now; restore the intended API before treating cached data as current.

If nothing matches, use Clear filters and inspect account/search/status selections before concluding that the record is absent. Explorer and Detail retain their view choices per item, so an old filter can still apply after reopening.

Follow a trade and its event details#

Choose Trades & Chart in Audit Detail, or press 1 while the detail panel has focus. The run header supplies retained run identity and KPIs such as realized P&L, closed trades, win rate, profit factor and broker errors. These are scoped to the selected run and its evidence.

Select a round-trip row or chart marker. The event inspector shows the selected event's fields, expandable metadata_json and Raw event JSON, plus the events associated with the selected trade. Use previous/next event controls to inspect the sequence. Show on chart focuses an event tied to a trade; Copy event preserves the exact event for investigation.

Read the actual chronology: request, validation, queued action, broker acknowledgment/rejection, fill and later protection/close events where present. A requested stop or close is not its applied broker result. For current strategy console output, open that session's Output in Strategies; Audit's Parameters & Code is retained configuration/source evidence, not a console-output stream.

The chart supports Candles + equity, Candles or Equity. Select UTC or Local for the detail timestamps and retain that zone in notes. Missing chart bars do not erase trade evidence: inspect the message and use Open Data Download when offered. The chart's displayed equity/round-trip projection is not a replacement for exact provider ledger entries or a complete account valuation.

Inspect authoritative Account Events#

Choose Account Events, or 2 with Audit Detail focused. Verify the account identity shown before reading the ledger. This view reads the resolved provider/environment/account ledger, which can contain account activity beyond the selected algorithm's own trade events.

Use All kinds or an operation-kind chip to narrow the ledger. Entries are newest first. Load older account events retrieves another page; check the loaded/total state before assuming the visible page is the full account record. Compare event times, provider order/deal identities, quantities, currency and payload details with the selected run's events.

No account ledger linked to this run means AMM cannot derive a complete account identity from that run's retained request. It does not mean the account had no events. If Show <account> ledger is offered, verify its proposed identity before choosing it; otherwise open the independently identified broker/account history. Do not pick a similarly named account to make an empty ledger disappear.

Recover parameters, request and stored code#

Choose Parameters & Code, or 3 with Audit Detail focused. Review the stored parameter values, expand Parameters JSON and Request (sanitized), and use their copy actions when preparing a reproducible support record. These are the values retained for that run, not necessarily the current saved launch form.

Recovered from and Recovered pos / ord identify recovery lineage and counts where recorded. Run on identifies the execution destination where available. Follow the recorded source run when diagnosing recovery instead of assuming a restarted algorithm began with an empty account.

Strategy code snapshot displays captured source when present. No strategy code snapshot was captured for this run is an explicit absence, not an instruction to substitute today's plugin source. Preserve the plugin/build identity alongside the run. Treat even sanitized requests, code paths and copied payloads as material to review before sharing outside your organisation.

Compare with broker history#

Open the matching Order History/Position History or broker-history view in Positions & orders. Match exact account/environment, provider IDs, direction, filled/remaining quantities and UTC times. Use a chart only as price context. An AMM marker is a projection of retained evidence, while a broker fill is a separate provider-reported fact.

Use this process for both manual and automated sessions. An algorithm can request protection, cancellation or a close that the provider later rejects. The final broker state matters more than an outgoing action or an isolated event row.

Interpret incomplete history#

History may begin after a position opened, contain only its exit, or depend on a provider's retrieval window. AMM can show exit-only details when opening evidence is absent. Keep missing evidence explicit; do not calculate an invented opening price or assume a missing row means no trade occurred.

Partial fills, netting and hedging change how orders relate to positions. Several fills can contribute to one net position. A single logical order can produce multiple execution records. Compare filled quantity, remaining quantity, direction and account identity before declaring a mismatch.

Show history on a manual chart#

Historical-trade overlays are independent from current positions and working orders and are off by default. Enable them through the chart's historical-trade display controls, then review the exact account/environment binding and chosen history range.

If the selected chart or broker context changes, verify history identity again. Never merge trades solely because their display symbols look alike. For research, use the run's own trades/orders ledgers; those are simulated execution records with the run's data and fill assumptions.

Reconcile after a connection failure#

When submission times out, first inspect actual broker working orders and positions. Then compare Audit and broker history. A request can have reached the provider even when the application did not receive the reply. Reissuing it immediately can duplicate exposure.

For recovered automated sessions, review reconciliation status and ownership before resuming. External/manual activity on a netted account can change the baseline used by virtual strategy allocation. Some providers expose dedicated sync health and repair workflows; use their provider guide and repair the complete intended cohort rather than arbitrarily editing one strategy's ledger.

Preserve useful evidence#

Keep non-secret order/deal IDs, event times, session/run identity, source version and the precise provider rejection text. Export available tables or reports through their own actions. Preserve server logs and audit storage according to your deployment's backup process; screenshots alone are incomplete incident records.

Before sharing a screenshot, remove or avoid account identifiers, balances, tokens, private paths and personal labels. A useful support record states what was requested, the actual result and whether the account remains exposed. Use the independent broker application for an urgent real-account state check.

Common outcomes#