Repair Continuous in Algo Trading: How to Fire Repeated Trades on a Condition

Meta description: Learn how Repair Continuous works in algorithmic trading — execute trades repeatedly on a condition, use runtime variables safely, and avoid infinite trade loops.

Repair Feature Series · Part 2 · 5 min read

In the previous part of this series, we covered Repair Once — a feature that fires a single corrective trade when a condition is met. Now it's time to understand its more powerful counterpart: Repair Continuous.

As the name suggests, Repair Continuous keeps firing trades as long as the condition remains true. That one distinction changes everything about how you design your logic.

What Is Repair Continuous?

Repair Continuous is a trade execution mode where the system evaluates a condition repeatedly and fires a new trade every time that condition is satisfied. There is no built-in limit to how many times it can execute.

This makes it ideal for strategies like averaging down — where you want to buy more each time the price meets a set condition from your last entry. But it also means that poorly written conditions can result in hundreds of trades firing within seconds.

Repair Once vs. Repair Continuous

Repair Once fires a single trade per trigger and stops after one repair execution. Repair Continuous, on the other hand, keeps checking and executing without any built-in stop. Repair Once carries a low risk of overtrading and requires an exit trigger after repair. Repair Continuous carries a high risk if logic isn't restrictive, and does not require a separate exit trigger. Repair Once is best suited for one-time adjustment trades, while Repair Continuous fits strategies like averaging down or grid-based entries.

The Critical Rule: Restrictive Logic

This is the most important concept to internalize when using Repair Continuous.

If your condition never becomes false after a trade fires, Repair Continuous will keep placing trades — potentially hundreds within a single second. This is not a theoretical risk. It can happen in live markets if the condition is even slightly loose.

Always structure your condition so it resets after each execution. The cleanest way to do this is by using a runtime variable as your reference point and updating it inside the repair trade block. Once updated, the condition is immediately invalidated, and it only re-triggers when the market genuinely moves to your next intended level.

Think of it this way: the condition should become false the moment a trade fires, and should only become true again when your actual trading scenario repeats.

How Active Quantity Affects Repair

One important behavior applies to both Repair Once and Repair Continuous. If the set-level active quantity drops to zero, no further repair conditions are evaluated.

This means if you use Repair Continuous to exit all open positions, the system will stop checking repair conditions entirely and revert back to checking entry conditions. Keep this in mind when designing any exit-focused repair logic — once your positions are fully closed, the repair layer switches off automatically.

Key Takeaways

Repair Continuous fires trades repeatedly while a condition is true, with no built-in stop. Always update a reference variable after each trade so the condition resets immediately. Unlike Repair Once, you do not need a separate exit trigger in Repair Continuous. If active quantity reaches zero, the system exits repair mode entirely and returns to entry-level evaluation. Always test with small quantities first — an unrestricted condition can fire hundreds of trades within seconds.

Up next: We'll combine Repair Once and Repair Continuous to build a complete averaging-down strategy from scratch.

Tags: Algo Trading · Repair Continuous · Runtime Variables · Averaging Down · Strategy Building · Automated Trading

Updated on: 07/05/2026