Order guardrails (max quantity, confirmation)
Order guardrails are application-side checks applied before an order leaves the platform: a maximum quantity per order, an optional confirmation step, and a daily loss limit. They reduce the cost of a wrong click; they do not replace the limits enforced by the broker or a prop firm.
Senzoukria · Glossary · Updated September 2026
Three kinds of guard
| Guard | What it checks | What it cannot do |
|---|---|---|
| Maximum quantity | Rejects a ticket whose size exceeds the configured number of contracts | Know the firm's contract cap for that account phase |
| Confirmation | Shows a recap and requires a second click before sending | Prevent a deliberate wrong order |
| Daily loss limit | Stops new sends once the day's realized loss reaches a threshold | Match a firm's rule computed on unrealized equity or a different session boundary |
Where the guard runs
The guard runs on the machine, before the request reaches the broker. That order of operations matters: a guard can block a send, but it cannot cancel something already accepted, and it cannot see fills made from another platform on the same account. A firm's daily loss rule is evaluated on its own servers with its own definition of the day; the two limits should be set so that the application's limit is reached first, and then verified against the firm's dashboard rather than assumed equal.
In Senzoukria
The guards live in Settings. Order confirmation has a Mode with two values: 1 click, send immediately, and 2 clicks, confirm first. The setting applies everywhere an order can be sent: the ticket, the chart quick ticket and the right-click menu. The tour lists the three guards together: maximum quantity, confirmation before sending, daily loss limit.
The strategy autopilot has its own Max daily loss ($) field, separate from the manual guards, and a STOP control that disarms the strategy and requests flattening. After a STOP, the desktop asks for a verification that positions and working orders were checked on the original broker account, because releasing STOP does not confirm a broker state.
Common mistakes
- Setting the application's daily loss limit equal to the firm's and expecting identical breach timing.
- Treating two-click confirmation as protection against a bad idea rather than a bad click.
- Forgetting that a maximum quantity per order does not cap the total position after several sends.
- Trading the same account from two platforms so that neither guard sees the whole day.
Related
- Order ticket
- AI assistant and the autopilot
- Orderflow software and prop firm rules
- Test a trading strategy
This page in other languages
Frequently asked questions
- Should I use one-click or two-click sending?
- Two clicks show a recap before the order leaves, so a mis-click costs nothing but a moment. One click sends immediately and suits situations where the trader accepts that risk. The desktop applies the chosen mode to every entry point, so the choice is made once in Settings.
- Does the daily loss limit satisfy a prop firm's rule?
- Not by itself. The application limit is computed locally on the fills it sees; a firm's rule may use unrealized equity, a trailing floor, a different session cutoff or a consistency clause. Set the local limit tighter than the firm's, then check the firm's own dashboard for the authoritative figure.
- Do guardrails apply to the autopilot?
- The autopilot has its own settings, including a maximum daily loss and explicit arming that is never persisted between sessions. Its STOP control disarms the strategy and requests a flatten. Manual guards and autopilot limits are configured separately and should both be reviewed before an account is connected.