Level 3 — Alarm Investigation¶
Classic explains alert-handling responsibility. This level teaches how to preserve the initial Alarm state in Edge, verify related views, establish scope and form evidence.
Goal and Core Flow¶
ALERT ≠ ROOT CAUSE. Preserve the initial visible state before opening more views. The object shown in the alert is only the starting scope; the confirmed impact scope must be established from further evidence.
Use when a visible alarm or condition requires attention.
Alarm Activity shows alarms that are currently in the Firing state. Recovered alarms leave Alarm Activity; use the historical Alarm view when recovery status is required. A current Firing state does not mean the Dealer's investigation is complete.
Official TradePass Alerts¶
Taker Symbol Dark
Severity: Critical.
Confirmed: the customer-facing Taker symbol is in the displayed alert condition.
Check: Symbol Overview → Connection Status → relevant Client Stream → Decision Stream.
Do not assume: that a Maker or LP caused the condition, or that all clients are affected.
Save / escalate: symbol, Server Time, alert state, quote freshness and relevant customer/order evidence; escalate promptly with confirmed scope.
Maker Symbol Dark
Severity: Warning.
Confirmed: a specific Maker × Symbol input feed is in the displayed alert condition.
Check: Symbol Overview, then relevant connection and quote evidence.
Do not assume: the entire Maker pool is dark or all customer quotes are affected.
Save / escalate: Maker, symbol, Server Time, alert state and confirmed downstream evidence; escalate if impact, persistence or scope requires it.
Common Investigation Patterns¶
These are Academy investigation patterns, not official TradePass alert names.
Connection Problem Investigation
Confirmed: visible connection evidence needs attention.
Check: Connection Status → category → exact link → Quote or Trade → status and heartbeat.
Do not assume: every path or the whole platform is down.
Save / escalate: Server Time, link, traffic, status, heartbeat and any confirmed downstream symptom.
Quote / Price Problem
Confirmed: a visible quote condition needs review.
Check: Symbol / Maker pool / Bid / Spread / Ask / Updated / LPs / M_micro, then related views only as needed.
Do not assume: a source, LP or rule is the cause.
Save / escalate: symbol, Server Time, displayed quote fields and reconciled evidence.
Reject / Order Problem
Confirmed: the displayed order result needs review.
Check: current Decision Stream view → Server Time → Order ID → Account / UID → result → connection/quote context.
Do not assume: a reject proves a connection, quote or platform cause.
Save / escalate: view, time, order identifiers, result and relevant context.
Before reading order evidence, confirm the Decision Stream view. Rejected only, a symbol/anomaly view and All orders are different scopes; a filtered stream is not complete order flow.
Escalate, Monitor or Handover¶
Use one factual update: Server Time → alert → observed facts → confirmed scope → evidence checked → material unknowns → current follow-up → next review. Continue after escalation: watch for change, preserve new evidence and hand over every unresolved item with an owner, next action and next review.
Scenario Practice¶
Taker Symbol Dark
At 14:06 Server Time, XAUUSD is shown dark and `Updated` is stale. Two relevant rejects appear. The confirmed scope is the displayed XAUUSD condition and those identified orders; cause and broader scope remain unknown. Preserve the alert, times and evidence, then escalate and monitor.Maker Trade Connection
The Quote link is healthy while the Trade link is disconnected. Report the affected Trade link and its heartbeat; do not describe the whole Maker path as down without evidence.Rejected only
The selected stream is `Rejected only`. It is a review queue, not proof that most or all orders are rejected. Confirm the wider observation scope before stating impact.Need more detail? See the Investigation Map, Evidence & Timeline and Escalation & Handover.