Alert
Records an Alert message on a control outcome; Backtests simulate delivery.
Records an Alert message on a control outcome; Backtests simulate delivery.
When to use
Use it for a user-visible notification on a meaningful control outcome.
Example
On Condition Match, send a message that includes the symbol and indicator value.
Make the message match the rule
For the RSI Starter, connect Condition: Match to Alert, choose the literal message source, and write BTCUSD RSI is above 60. If you later raise the Condition threshold to 65, update the message too; the text does not automatically follow the comparison parameter. If you choose the data-port message source instead, connect a compatible string output to Message. A numeric Indicator output cannot be connected as message text without a supported conversion.
Alert's configured delivery target describes the product target, but a Backtest records a simulated Alert event and does not email the account. The node has a Next continuation; it does not prove that an Order was submitted or filled. When checking a run, inspect the event, the branch that reached Alert, and the actual message. Consecutive bars above a simple Greater-than threshold may produce repeated Match activations.
Common problems
Alert needs a control arrival. Keep messages clear and avoid assuming that an alert proves an order or rebalance succeeded.
Next steps
Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.
In a Backtest, the Account Email target produces a simulated event without sending an email. Saving the graph alone does not activate delivery.
Related documentation
- String TemplateBuilds a readable message from a template and connected values.
- Build an RSI Momentum AlertCreate the Starter strategy, change its threshold, validate it, save it, and reopen it.
- Backtests and responsible useInterpret simulated results with appropriate limits and avoid treating them as predictions or advice.