Safety Trigger

Starts a bounded auxiliary safety path when a supported measure crosses its configured threshold.

When to use

Use it alongside the required primary Schedule Trigger when a Portfolio strategy needs a defensive response to a supported safety breach.

Example

With the primary Schedule Trigger already present, begin a defensive path when the selected safety condition breaches its limit.

Try it here

Explore Safety Trigger

Starts a bounded auxiliary safety path when a supported measure crosses its configured threshold.

Exercise steps

1. Select Safety Trigger and change the drawdown threshold.
2. Follow its dedicated path to Halt and inspect the all-activations cleanup policy.

Start lesson

Keep the guard separate

In a scheduled Portfolio strategy, keep Schedule Trigger as the primary activation. Configure Safety Trigger to watch one supported engine metric, an operator, a threshold and an evaluation frequency. An illustrative drawdown rule is “fire when drawdown crosses the configured limit”; check the metric's unit and operator before entering a threshold. The Breach Value output can help an Alert explain what the guard observed.

Connect Safety Trigger → Alert → Halt, or the allowed direct Halt route with its required cleanup policy. The guard must not join the ranking/rebalance path and Safety Trigger → Order is not an allowed way to place a defensive trade. In a historical run the Alert is simulated; inspect the guard event and Halt outcome instead of assuming an email or a live position change.

Common problems

It is an auxiliary guard, not a primary activation. Keep the required Schedule Trigger and connect Safety Trigger only to Alert, a correctly configured Halt, or Alert followed by Halt. It cannot join the primary path.

Next steps

Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.