Decision Stream¶
Purpose¶
Decision Stream is the real-time view of order decisions and outcomes. It provides operational evidence; it is not an approval or order-modification screen.
Confirm the Scope First¶
Before investigating, confirm which order-flow view/subscription you are currently looking at. A filtered stream is not the complete order flow.
Rejected only, a symbol or anomaly view, and All orders are different monitoring scopes. A visible cluster may describe the selected view rather than the complete live flow. Do not investigate a filtered stream as if it were all orders, and do not teach or alter subscription implementation.
Read the Subscription Panel¶
The real Decision Stream interface keeps its selected monitoring scope in the Subscriptions panel. This sanitised screenshot-style guide shows what a Dealer needs to read, not how to create, edit or delete a subscription.
- All orders: use it when you need the broadest available order-flow context within Decision Stream. It is not the complete evidence set for an Incident.
- Rejected only: it is an investigation queue, not proof that all or most orders are rejected.
- Symbol / anomaly view: it narrows the evidence to a selected scope. Record its name and time with any finding.
The panel may contain other approved views. A Dealer reads the selected scope and preserves it as evidence; only authorised personnel manage subscription definitions and conditions.
If the Panel Is Idle¶
After a full page refresh, the active panel selection can reset and Decision Stream can show Idle. If this happens, confirm and activate the existing desk-approved monitoring subscription(s) before assuming order flow is unavailable. This means selecting an approved existing view only; do not create, edit or change a subscription.
Where to Find the Evidence¶
- View / subscription: confirm the monitoring scope first.
- Order ID: the primary record identifier to preserve.
- Account / UID: establishes which account context is involved.
- Symbol: identifies the affected product.
- Server time: anchors the investigation timeline.
- Decision / result and visible evidence: preserve what the page actually shows; do not infer a root cause from a result label alone.
What Normal Looks Like¶
Records arrive continuously within the selected scope, timestamps are coherent, and each result can be matched to the relevant order and account context.
What Needs Review¶
Review repeated rejections or timeouts, missing or delayed records, a cluster by symbol, client or time, or a result that conflicts with related evidence. First determine whether the pattern is isolated to an account, rule context, route or wider market condition.
Shift Action¶
- Confirm the current view or subscription and record it with the incident evidence.
- Build a timeline using Order ID, account / UID, product, server time and visible result.
- Compare the same window in quotes, Connection Status, Client Stream and relevant order context.
- Escalate material client impact, clustered failures, missing evidence, repeated unexplained outcomes or suspected wider degradation.
Reminder¶
Decision Stream is evidence. Use only within assigned Dealer authority; never modify or cancel an order without specific authority.
Previous: Client Stream · Next: Level 2 - Client & Account Investigation →