Monitor, stop and recover automated trading

Verify the start completed#

After Review & start…, a session can progress through Pending and Warming up before Running. Admission acknowledges that the request was accepted; it does not mean warmup, subscriptions and broker recovery have finished. Verify the final session state, account, symbol, effective graph and feed health.

A portfolio has child sessions. Partly running · N of M means some children failed. Inspect each reason; do not treat the parent as universally active. Multiple same-symbol rows can be intentionally independent instances, so use instance/session identity when acting.

Read the fleet and selection#

The Sessions table defaults to Algorithms. All also shows manual chart/trading sessions; the footer explains hidden manual sessions and offers Show. Hidden rows are not bulk Start/Stop/Remove targets. The summary strip remains algorithm-focused.

Rows expose state, algorithm, symbol, timeframe, broker account, data route, portfolio, bars/trades/positions, P&L and heartbeat, with additional columns in the chooser. P&L totals remain separated by currency. Selecting a row drives the exact Details, Chart and Output context.

The right-side Selected | All sessions choice determines the position/trade scope. Equal broker IDs across accounts remain separate. For netted brokers, a session allocation can differ from the full account's net position; inspect source/ownership before closing it.

Interpret feed health separately from lifecycle#

Hover for last tick age, broker-link evidence and provider detail. Quiet during a scheduled inactive interval is different from a disconnected subscription. A nominal Running lifecycle does not override unavailable price input. Entry/debug/close actions can be blocked when input cannot be trusted, while Stop remains available when the API is connected.

API disconnection is separate: cached rows are labelled disconnected and mutations are disabled. Restore the intended server rather than repeatedly clicking Start against stale UI state.

Inspect details, routes and output#

Details shows effective instruments/accounts, provider routes and configuration. Chart instrument selects an exact graph instrument; its bars, indicators and trade/order levels follow that identity. Output contains lines for the selected session and can be filtered by level. Clearing Output affects displayed lines, not the trading audit or broker history.

Use View details, Instruments or View output from row actions. Compare errors with order lifecycle, broker history and execution-account sync status. A healthy price feed does not prove that broker reconciliation is healthy.

Supported manual actions appear in Actions. Position/order targets and account mode determine confirmation. Algorithm-owned targets route through the manual-override review. Optional plugin actions are available only when that algorithm advertises them; their presence is not universal across plugins.

Stop, restart or edit deliberately#

Stop always reviews owned exposure. Choose whether to close at market first, and inspect the resulting broker execution. Stopping alone and process shutdown do not liquidate broker positions. Broker-native protections can survive; AMM-managed protection needs its processing authority running.

Remove is disabled until a running session is stopped and asks for confirmation. It removes an entry, not an instruction to liquidate broker exposure.

Restart uses the saved recovery mode and can adopt matching surviving orders/positions without resubmission. Restart (clean start) / Clean Start uses a one-time no-recovery override. It does not change the saved default, and it does not close whatever the broker already holds. Review external exposure before using it.

Edit configuration… and Duplicate to launch… serve different purposes. Duplicate creates a new instance key for review. Running configuration updates can require a restart; remote configuration mutation is restricted. Read the presented review and preserve the existing definition before a substantial change.

Save portable definitions#

Save a running configuration through the row action or edit/save workflow. Saved configurations reopens exact requests, including parameter and connection-graph settings. Export omits credentials and prior approvals. Import checks installed plugins and account mappings and does not save/start automatically.

Connections on a destination server must still exist. A saved credential-profile reference is not a credential package. Explicit live account review is required when deliberately starting the imported configuration.

Recover after outages and restarts#

Before reconnecting/restarting, inspect broker positions and working orders on the exact environment/account. Recovery matches broker and strategy identity; a similarly named algorithm is insufficient. Check recovered trades and running P&L against retained audit lineage and attributable broker history.

Do not assume API process startup automatically resumes trading. Orphaned broker exposure can remain after a process stops, and auto-resume depends on deployment configuration. Desktop runtime restoration is a separate convenience and does not replace broker-state verification.

On Alpaca virtual allocations, Reconcile Broker State repairs supported broker-backed drift. The Adjust history records allocation corrections. Use that explicit repair path after diagnosing the account cohort; starting another duplicate strategy is not a drift repair.

For remote sessions, the worker is the executor. Control/status are proxied through the manager; stopping the UI or manager does not establish the worker's broker state. Inspect worker health and use risk controls for the intended scope. Preserve session, account and audit IDs when escalating an unresolved recovery error.