Stopping and restarting
Distinguish session lifecycle controls, process termination, and broker account actions.
Choose the operation based on what must change: strategy processing, the in-memory instance, the hosting server, or account exposure. These have different effects.
Session and server operations
| Operation | What to verify |
|---|---|
| Pause/stop processing | The selected runtime stops its loop or subscription as implemented; account exposure can remain |
| Start/resume an existing instance | Existing in-memory state may remain; this is not a clean historical replay |
| Restart a stage session | The current instance is stopped/destroyed and rebuilt from its associated saved app |
| Launch another server | A separate run is created; an earlier server or broker order may still exist |
| Terminate the server | Hosting resources stop; stored results and broker account state have separate lifecycles |
| Delete a server record | A history/record operation, not a replacement for checking account exposure |
Controls and exact cleanup behavior depend on the runtime. The generic pause retains its object; the RDX pause unsubscribes from input. Neither establishes a universal reset or close-position contract.
Before restarting a changed candidate
Save the intended source and settings. Check whether the running session uses the original app or a launch-specific copy. A restart rebuilds from the app associated with that runtime, which is not a promise to load whichever original editor you last changed.
Record pending orders, positions, and any diagnostic state you need. Script state and automation mode are not guaranteed to survive a new instance. Warmup and data initialization can run differently from a resume of the existing object.
Confirm the account separately
Check outstanding orders and positions before and after the lifecycle operation. If the goal is to cancel or close, use the appropriate explicit order/account operation and verify its result. A stopped process cannot be relied on to keep managing an existing position.
Do not interpret a successful restart response as completion of broker reconnection, warmup, or order reconciliation. Recheck data timestamps, logs, account state, and automation mode.
Multiple apps share infrastructure
Stopping a follower session is different from terminating its leader's server. Group termination is routed through the leader and affects shared resources and follower records. Review the selected run and group before acting.
Continue with multiple apps and troubleshooting.