Fix CI/CD Pipeline Flow

• Tier: Premium, Ultimate
• Add-on: GitLab Duo Core, Pro, or Enterprise
• Offering: GitLab.com, GitLab Self-Managed
• Status: Beta

Version history

• Introduced as an experiment in GitLab 18.4 with flags named duo_workflow_in_ci and ai_duo_agent_fix_pipeline_button. duo_workflow_in_ci is enabled by default. ai_duo_agent_fix_pipeline_button is disabled by default. These flags can be enabled or disabled for the instance or project.
• Enabled on GitLab.com and GitLab Self-Managed in 18.5.

The availability of this feature is controlled by a feature flag. For more information, see the history.

The Fix CI/CD Pipeline Flow helps you automatically diagnose and fix issues in your GitLab CI/CD pipeline. This flow:

• Analyzes pipeline failure logs and error messages.
• Identifies configuration issues and syntax errors.
• Suggests specific fixes based on the type of failure.
• Creates a merge request with changes that attempt to fix a failing pipeline.

The flow can automatically fix various pipeline issues, including:

• Syntax and configuration errors.
• Common job failures.
• Dependency and workflow issues.

This flow is available in the GitLab UI only.

Prerequisites

To use this flow, you must:

• Have an existing failed pipeline.
• Have at least the Developer role in the project.
• Meet the other prerequisites.

Use the flow

To fix your CI/CD pipeline:

1. On the left sidebar, select Search or go to and find your project.

2. Select Code > Merge requests and open your merge request.

3. Select the Pipelines tab.

4. In the rightmost column, for the failed pipeline you want to fix, select Fix pipeline with Duo.

5. To monitor progress, select Automate > Agent sessions.

   After the session is complete, go back to your merge request.

6. Review the merge request and make changes as needed before merging.

What the flow analyzes

The Fix CI/CD Pipeline Flow examines:

• Pipeline logs: Error messages, failed job outputs, and exit codes.
• Merge request changes: Changes that could have caused the failure.
• The current repository contents: For identifying syntax, linting, or import errors.
• Script errors: Command failures, missing executables, or permission issues.