Use Armed Setup Protection

Armed Setup Protection controls how long an already-valid setup is allowed to wait for entry and which pre-entry price events should retire it early.

It is a lifecycle protection layer. It does not make a strategy easier to qualify and it never bypasses setup, market-context, confirmation, or entry rules.

Set the maximum wait for entry

The Maximum wait for entry timer limits how long an armed setup remains available when entry never arrives.

The editor provides 1m, 3m, 5m, and 10m presets plus a custom minute value.

When the timer expires, the old armed setup stops waiting instead of remaining available indefinitely.

Retire the setup when stop or invalidation is touched

Enable Stop / invalidation touched when the setup should retire if its planned stop or invalidation level is reached before entry.

This avoids treating a setup as still valid after price has already crossed the level that was supposed to invalidate its pre-entry thesis.

Retire the setup when TP1 is reached first

Enable TP1 reached first when you do not want to enter after price has already reached the first planned target without filling the intended entry.

This is useful for avoiding stale entries after the move has already travelled through the main initial objective.

Retire a missed entry that moved too far toward TP1

Enable Too far toward TP1 and choose the percentage of the original entry-to-TP1 path that price may travel before the setup is retired.

For example, the control can retire an entry once too much of the original target path has already been consumed.

Retire after an adverse move away from entry

Enable Too far away from entry and set the point distance when an armed setup should retire after price moves too far in the adverse direction before entry.

Use an instrument-appropriate value rather than copying a point distance from a different market.

Playbook rules and strategy overrides

Setup Protection can exist at Playbook level. Supported strategy editors can either inherit the Playbook rule or use a strategy-specific override.

Inheritance is useful when the same lifecycle policy should apply across the Playbook. A strategy override is useful when one strategy genuinely requires a different maximum wait or early-retirement behavior.

What Setup Protection does not change

Setup Protection does not:

• make a failed setup condition pass;
• override a required Strategy Block;
• change market-context requirements;
• bypass entry filters;
• change post-entry break-even or trailing rules.

It only decides when an already-armed setup should stop waiting for entry.

For the separate control that decides when the same factual setup may receive another finite-entry quota, see Configure same-setup re-arm.