Exit Conditions are preset rules that end an automation when any one of them becomes true.
Treat them as a safety switch that can stop a run regardless of where it is in the flow.
How Exit Conditions work
- Exit Conditions are preset at the automation level and evaluated continuously while the run is active.
- When any exit condition becomes true, the current run stops immediately.
- You can add multiple preset rules; they are checked in parallel during execution.
FYERS Web
- Open your automation on the canvas.
- Click Exit conditions on the top bar.
- Add one or more preset rules (for example: P&L threshold, order status, symbol attributes, time window).
- Save. The run will stop the moment any of the rules becomes true.
Notes
- Exit Conditions stop the run only. If you also want positions closed, place a Square off action before your stop points or handle exits operationally.
- Keep presets simple and decisive—use the minimum number of rules needed to express your exit logic.
What If...
| Scenario | Outcome |
|---|
| I add multiple preset rules | The automation stops when any one rule is met. |
| A preset rule becomes true mid-execution | The run stops immediately; remaining nodes do not execute. |
| I also need open positions closed when stopping | Add a Square off node before the stop point, or close positions operationally. |
Last updated: 22 Dec 2025