## Overview ## **Feature overview:** Fix Failing Pipeline Flow Next upgrades the Fix Failing Pipeline Flow by replacing `fix_pipeline/v1` with `fix_pipeline_next/v1`, improving the quality and usability of the flow ## **What's New** ## Core Improvements 1. The flow intelligently delivers fixes where they matter most: as code suggestions on your existing merge request, or as a new merge request. 2. Pipeline failures in child pipelines are now included in the analysis, so the flow catches issues across your entire pipeline hierarchy ,not just the top-level pipeline. 3. Customize how the flow behaves in your repository by adding an `AGENTS.md` file — control commit message format and merge request metadata. ## UX Improvements 1. MR comments and descriptions generated by the `fix_pipeline_next` flow are now minimal by default, with verbose AI reasoning collapsed behind expandable `<details>` sections. Comments no longer dump the full analysis inline — users see a clean summary and can expand for more context if needed. 2. git commits created by the flow now use the triggering _user_ as the committer (and the service account as git author), while MR creation is also attributed to the user 3. Flow start and completions are posted as system notes to the MR ## Goals This epic tracks the full rollout and cleanup of the `fix_pipeline_next` feature flag, graduating the improved Fix Pipeline flow from a gated experiment to the default experience for all Duo Agent Platform (DAP) customers on GitLab.com. 1. **Enable `fix_pipeline_next` globally on GitLab.com** — incrementally roll out the feature flag to 100% of customers, monitoring error rates and flow behavior at each step. 2. **Remove the feature flag** — once the rollout is stable, clean up the flag from the codebase and replace all references to the legacy `fix_pipeline` flow with `fix_pipeline_next`, ensuring customers using DAP are automatically upgraded to the new flow without any manual intervention. 3. **Validate backward compatibility** — before removing the flag, verify that past GitLab versions are compatible with `fix_pipeline_next`, specifically confirming that all flow inputs used by the new flow are supported across the relevant version range. ## Rollout Plan - Incrementally enable `fix_pipeline_next` on production using chatops, starting at a low percentage and increasing while monitoring dashboards. - After reaching 100% and observing stability for at least one day, proceed to flag removal. - Communicate the change to `#support_gitlab-com` and the team channel before global rollout. ## Flag Removal When removing the feature flag: - Replace all conditional references to the legacy `fix_pipeline` flow with `fix_pipeline_next` as the unconditional default. - Remove the YAML feature flag definition and all code branches guarding the old flow. - Ensure the cleanup MR is included in the release package and the feature flag is deleted from all environments (`--dev --pre --staging --staging-ref --production`). ## Backward Compatibility Validation Before removing the flag, validate that `fix_pipeline_next` is compatible with past GitLab versions that may still be in use. This includes: - Auditing all inputs consumed by the `fix_pipeline_next` flow. - Confirming each input is supported in the relevant older GitLab versions. - Documenting any version constraints or required minimum versions. ## **Acceptance Criteria** Before the rollout on GitLab.com - we need to ensure the following conditions are met. \[ \] `fix_pipeline_next` quality outcome targets are met - See https://gitlab.com/gitlab-org/gitlab/-/work_items/592934#quality-metrics \[ \] `fix_pipeline_next` cost should not exceed YTD p25, p50,p 75, p90, p99 credits compared to 'fix_pipeline' ## **Success Metrics** | Metric | Current | Target (FY27Q4) | |--------|---------|-----------------| | Monthly Flow Sessions | \~4000 | \~16000 | ## Definition of Done - [ ] `fix_pipeline_next` enabled at 100% on GitLab.com with no regressions. - [ ] Backward compatibility of all flow inputs confirmed across supported GitLab versions. - [ ] Feature flag removed from codebase and all environments. - [ ] Legacy `fix_pipeline` flow replaced by `fix_pipeline_next` as the default. - [ ] Documentation updated with version history text. - [ ] Rollout issue closed.