Live Runtime

AQE runs your strategy, processes broker responses and maintains insight state. AQS displays that state and lets you request operational actions. A healthy desktop connection and a healthy trading process are separate things: check both when supervising a live strategy.

From decision to execution

An alpha model creates an insight. State-specific pipes validate it, size it and request broker operations. Submission, cancellation, replacement and closure can remain pending while the broker responds.

A queued request is not a confirmed fill. Follow the insight state, broker order identity and recorded history to establish what happened. Custom pipes must preserve deferred results rather than treating a full queue or a pending response as a rejected trade. See Insight Pipes.

Read live health correctly

Use the strategy detail view to check the runtime status, latest account observation, insight activity and synchronisation health together.

Observation	What to check
Running strategy, stale dashboard	Check connectivity and the age of the latest observation before assuming execution stopped.
Pending critical events	The delivery system still has execution-related updates to forward.
Reconciliation in progress	Recovery is checking retained records against execution history. Review unresolved items before restarting.
Dead-letter entries	Some updates require investigation; local acceptance alone does not prove cloud delivery.
Stopping	Teardown is still in progress. Wait for the final outcome and inspect any reported error.

The current runtime separates broker work, local persistence and cloud delivery. This reduces the amount of work performed directly in the strategy loop, but does not promise a fixed broker or network latency.

Recovery and session identity

A strategy, its live session and a particular run have different identities. Historical records must remain associated with the correct owner and run. A restarted process can recover retained execution work and reconcile history; an old dashboard row is not proof that an order is still active.

Avoid launching a replacement process simply because the desktop temporarily loses contact. Check the original runtime and broker account first. The current AQS deployment path checks broker-account execution ownership and can refuse a conflicting launch.

Stopping a strategy

Open the strategy detail view and request Stop.
Keep the view open while the status shows Stopping.
Review teardown progress and the final status.
Check the broker terminal for remaining positions or pending orders if teardown reports a problem.

An application update does not change an already-running strategy executable. Rebuild and restart only after checking the previous run and its broker exposure.

Local and cloud observations

AQE’s terminal interface reads local snapshots. AQS Cloud displays delivered records. Each can lag for different reasons. Local acknowledgement means an update was accepted locally; it does not confirm that the cloud or desktop has received it.

Runtime logs are retained locally in the current implementation. Use the editor or execution host for those logs; use strategy events and insight history for the cloud-visible operational record.

For the desktop workflow, see Live Strategies.