Start Strategy
The Start Strategy rule controls when your trading strategy begins execution. You can configure it to start immediately when deployed or on a recurring schedule using a cron expression. It also includes a safeguard to limit the number of concurrent strategy instances, preventing accidental duplicate deployments.
How It Works
The Start Strategy rule serves as the initialisation signal for your strategy. When set to start immediately, the strategy begins processing rules and evaluating conditions as soon as it is deployed. When configured with a schedule, the strategy waits until the cron expression matches before activating, allowing you to align strategy start times with specific market sessions or events.
The deployment limit safeguard is an important safety feature. When enabled, it checks how many instances of this strategy are currently running and prevents new deployments from starting if the maximum number of concurrent deployments would be exceeded. This protects against accidentally launching multiple copies of the same strategy, which could lead to unintended position sizes or conflicting orders. The default limit is one concurrent deployment.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
| Start Immediately | Boolean | Yes | When enabled, the strategy begins execution as soon as it is deployed. When disabled, the strategy waits for the configured schedule. Default: true. |
| Schedule (Cron) | Cron Expression | No | An optional cron expression that defines when the strategy should start. Uses the format: Seconds Minutes Hours DayOfMonth Month DayOfWeek. |
| Limit Deployments | Boolean | Yes | When enabled, restricts the number of concurrent instances of this strategy that can be running at the same time. Default: true. |
| Max Concurrent Deployments | Number | Yes | The maximum number of instances of this strategy allowed to run simultaneously. Only applies when Limit Deployments is enabled. Default: 1. |
Outputs
| Output | Type | Description |
|---|---|---|
| This rule does not produce any outputs. It acts as a strategy-level control signal. | ||
Tips
Keep Limit Deployments enabled with a max of 1 when you are developing and testing strategies. This prevents accidentally running multiple copies during iterative development. If your strategy is designed to run multiple independent instances (for example, one per symbol in a multi-symbol setup), you can increase the max concurrent deployments accordingly. Use the schedule option to align strategy starts with your preferred trading sessions, such as starting at the London open each weekday.
Was this helpful? Let us know