Repair loops
A defect found during verification can drive a bounded repair-then-reverify cycle instead of immediately failing the task.
AgentDock Pro
Repair loops are part of AIgency, available only in AgentDock Pro.
When verification finds a genuine defect rather than a passing result, AIgency doesn't necessarily fail the task outright — it can drive a repair iteration first.
The repair cycle
A repair iteration moves through its own status lifecycle: repairing (an agent attempts a fix) → reverifying (verification runs again against the fix) → resolved if it now passes, or limit_reached / stopped if it doesn't and the loop has run out of budget.
Warning
Repair iterations are bounded. AIgency will not loop indefinitely trying to fix the same defect — once the limit is reached, the defect is left for you to resolve manually rather than continuing to spend agent turns on it.
Defect outcomes
A defect found this way carries its own status independent of the repair-iteration status: open, repairing, resolved, accepted (a known issue you've chosen to accept as-is), rejected, or cannot_reproduce. These are recorded in the run's history regardless of how the repair loop ultimately concludes — see Run history.