Halt
Stops the current trigger path or all active trigger paths according to its configuration.
Stops the current trigger path or all active trigger paths according to its configuration.
When to use
Use it for an intentional terminal outcome such as a safety stop or unrecoverable branch.
Example
After a critical safety outcome, halt the relevant path with the required cleanup behavior.
Decide what stopping means
Connect a critical branch to Halt and choose whether the current activation or all activations should stop. Then set the required cleanup policy deliberately: cancel open orders, cancel and close exposure, or leave runtime state as it is. For a Portfolio Safety Trigger guard, only the allowed Halt configuration is valid; check validation before assuming an all-activations cleanup is available on that route. Halt ends control flow, but cleanup actions can have their own outcomes and cannot undo an earlier fill. Verify the recorded stop and affected orders or positions in the run result.
Common problems
Halt is terminal. Confirm whether the scope is the current path or all paths, and review pending-order cleanup before relying on it.
Next steps
Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.
Related documentation
- Safety TriggerStarts a bounded auxiliary safety path when a supported measure crosses its configured threshold.
- Cancel OrdersRequests cancellation for one pending order or for open strategy orders.
- Tactical order and position monitoringUnderstand a Tactical pattern that sizes an order, checks margin, tracks its lifecycle, and monitors the position.