<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=482846) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Context Failed pipelines get created due to configuration validation issues, in addition to the original pipeline that got manually triggered. These pipelines are often unexpected by users as they do not show up when the CI job run successfully. When the failed job is due to access issues of the group/project access token, the owner of the failed pipeline is the group/project bot instead of the user running the original pipeline, which adds to the confusion. I don't think this behavior is currently documented. Some users may find out about this behavior due to trial-and-error. However, users not familiar with this may end up spending time troubleshooting the origin of the unexpected pipelines created. There are several scenarios of this issue showing up: 1. https://gitlab.com/gitlab-org/gitlab/-/issues/421811 - According to @lma-git: > When all jobs are ruled out due to `include:rules`, it's treated as a config validation error, which results in a failed pipeline. When all jobs are ruled out due to `job:rules`, it's treated as a pipeline population error, in which case the pipeline is not created/persisted. 2. https://gitlab.com/gitlab-org/gitlab/-/issues/361993 3. Project access denied with `include` - Users may get insights on the origination of the error by hovering on the description on the failed pipeline:  ### Proposal According to [this](https://gitlab.com/gitlab-org/gitlab/-/issues/421811#note_1510237186) comment, addressing the behavior is considered a feature request rather than a bug. Proposal to address this issue: 1. Document the behavior 2. Enhance the text/UX when the failed pipelines get created <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->