Configure independent automated strategy instances

View full-size screenshot ↗

Choose one instance or a portfolio#

Open Strategies. One configured instance is one complete algorithm request with its own symbol, timeframe, parameters and connection graph. The same algorithm can run in several instances, even on the same symbol. Instance identity is separate from algorithm name and ticker.

Adding several Symbols in the launch pane creates independent instances in a portfolio. It does not turn an algorithm into a single multi-instrument strategy. Code-declared instruments and data-only dependencies remain inside their owning instance's graph.

Configure a single instance#

1. Choose the exact algorithm in its plugin folder. Review changed parameters first; All N parameters… opens the full staged editor. Groups separate Strategy, Position sizing and Execution policy.
2. Choose the exact Broker account and symbol. Its label shows account mode and available facts. Demo/Paper is an external broker account, distinct from AMM Simulation.
3. Review Data feeds. Same as broker is the compact default; Change… opens separate Live data and Historical data connections. Review Symbol on broker and the Route line.
4. Use Check… → Check route to validate the route. Read per-role contract comparisons and any Not checked result. This check is not permission to start trading.
5. Review timeframe, Run on, warmup, indicator history, DATA options, ALGORITHM POLICY and folded Risk & recovery.
6. Save if you want a reusable definition. Choose Review & start… only when you intend to start, then review every resolved account and complete required live approvals.

A connected broker account supplies its real/demo/paper funds. Multiple instances on the same account share that balance. Starting cash is not an individual algorithm reservation. Simulation starting balance appears only when the execution Broker is Simulation; choosing a simulation data feed alone does not create a virtual execution budget.

Use the portfolio table#

Edit each in table…, Open as portfolio table… or Configure portfolio opens the instance table. It groups rows by broker account and shows Symbol, Algorithm, TF, Data, Changes and Status. Search, Group and Columns help manage a larger set.

Click a row background to inspect it. A checkbox adds a bulk-edit target. These are separate actions: focusing a row does not replace the checked set. Hidden checked rows remain selected when you search, so read the selection count before applying changes.

Click Symbol, Algorithm or TF to open its picker. Duplicate in the focused editor copies that row with a fresh instance key. Checked-row Duplicate copies the selected targets. Neither creates shared parameter state.

Add symbols… lets you choose the account, exact instruments and a Copy settings from template. Review Will add N instances, including timeframe and broker. Equal ticker text on different sources remains distinct. New symbol rows do not inherit unrelated provider aliases from a template.

Apply bulk changes deliberately#

Choose Edit N…. Each field shows the selection's existing values and offers an empty replacement. Empty means keep each row's own value. A changed field reads Will change and can be undone before Apply N changes.

Parameter edits group by exact installed algorithm folder/name and matching parameter declarations. A similarly named parameter in a different plugin is not automatically eligible. Replacing an algorithm loads its own defaults; reselecting the same algorithm preserves overrides. Simulation-only controls apply only to Simulation execution rows.

The summary counts changes and affected instances. Discard or closing the editor leaves rows unchanged. Moving focus with a pending edit prompts for apply/discard/continue rather than silently losing it. Review the table preview before saving or starting.

Understand hours options#

Include extended-hours data requests supported data/routing. Allow extended-hours entries affects only algorithm helpers that actually consume that policy. Enforce assigned trading hours applies the assigned Instrument Manager calendar gate to AMM execution and locally managed protection.

These controls are independent. A disabled option explains that the algorithm does not read it. Effect now and Compare combinations describe the actual applicability. Missing calendars add no calendar restriction; enabling data does not grant broker permission. Calendar enforcement can suppress AMM-managed SL/TP processing outside its hours, while broker-native protections retain broker behaviour.

Save, import and export#

Save changes updates the loaded record; Save as new… creates another. A portfolio Save keeps the table open. Saved configurations offers Edit, Start…, Export JSON…, Duplicate, Rename… and confirmed Delete… . An unreadable record can offer Repair into a new draft without rewriting the original.

Export shows instance/account/symbol counts and portable JSON. Credentials and prior approvals are omitted. Copy leaves the preview open; Download saves the file. Import reads a file or pasted JSON, checks installed algorithms/accounts and offers mapping for missing connections. Opening the imported rows saves nothing until Save.

Every start path uses account preflight and one account review. Typed LIVE is required for each distinct live account; unknown mode is treated as live. Cancelling keeps the draft. A portfolio can start only partly if some children fail, so inspect its reported running/failed counts after dispatch.

Recover a blocked launch#

For a missing plugin, install the exact plugin and preserve existing parameter values. For route failure, correct exact connection/symbol metadata; do not rename a ticker merely to pass admission. For invalid size, use current broker limits. If account approval is declined or preflight fails, the editor remains open. Once started, use Automated trading operations to verify actual health and execution.