Back to tips
    How to Use the Rollback Feature: Recovering from Failures

    How to Use the Rollback Feature: Recovering from Failures

    Introduction

    Sometimes jobs executed with DevLoop Runner don't produce the expected results. In such cases, you can use the rollback feature to revert to a specific phase and retry.

    What is Rollback?

    Rollback is a feature that rewinds the workflow state to a specific phase and re-executes from there. For example, if there was a problem in the "implementation" phase, you can go back to the design phase and redo the implementation.

    Two Modes

    Auto Mode (Recommended)

    AI analyzes the current state and automatically determines the optimal rollback point.

    Features:

    • Execute with one click
    • AI analyzes problem areas
    • Automatic optimal phase selection

    How to use:

    1. Click "Rollback" button on the job detail page
    2. Confirm "Auto" mode is selected
    3. Click "Execute"

    Manual Mode

    You specify the target phase for rollback yourself.

    Features:

    • Fine-grained control possible
    • Provide hints to AI by describing the reason
    • Explicitly specify a particular phase

    How to use:

    1. Click "Rollback" button on the job detail page
    2. Select "Manual" mode
    3. Select the phase you want to revert to
    4. Describe the reason for rollback
    5. Click "Execute"

    Rollback-able Phases

    • Requirements (requirements)
    • Design (design)
    • Test Scenario (test_scenario)
    • Test Implementation (test_implementation)
    • Implementation (implementation)
    • Testing (testing)
    • Documentation (documentation)
    • Report (report)

    Effective Usage

    When to use Auto Mode

    • When you don't understand the cause of the error
    • When you want to let AI make the decision
    • When you want to recover quickly

    When to use Manual Mode

    • When the problematic phase is clear
    • When you want to redo a specific design decision
    • When you want to give AI additional context

    Tips for Rollback

    When describing the reason in manual mode, being specific helps AI respond more appropriately:

    Good Example

    The database query in the implementation phase is inefficient.
    N+1 problem is occurring, please fix with an efficient query using JOIN.
    

    Bad Example

    It doesn't work
    

    Summary

    • Auto Mode: Best for unknown causes or quick recovery
    • Manual Mode: Fine control when the problem is clear
    • Reason Description: More specific = better AI response

    By utilizing the rollback feature, you can develop without fear of failure. When problems occur, just go back to the appropriate point and try again.

    Get Started with DevLoop Runner

    Auto-generate PRs from GitHub Issues. Let AI accelerate your development.