### Problem to solve [Customer encountered](https://gitlab.zendesk.com/agent/tickets/161875) (internal only) an issue where in a scheduled pipeline will not run (even when ran manually via the `CI/CD -> Schedules` UI). It turns out that the there is a logic error in `.gitlab-ci.yml` where the main job uses the `needs` keyword and pointed to a job that has `except:schedules` set. ### Intended users * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### User experience goal The user should be able to see a helpful error message either in the `CI/CD -> Schedules` or `CI/CD -> Pipelines` when a scheduled pipeline failed to be created due to logic error in `.gitlab-ci.yml`. ### Proposal Add a pipeline schedule status to reflect that the scheduled pipeline was not created as scheduled. https://gitlab.com/gitlab-org/gitlab/-/issues/224958#note_1382437360 ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> Steps to reproduce scenario: 1. Create a project 2. Add the following as the CI configuration that passes lint checker ```yaml build: stage: build script: echo test: stage: test needs: ['build'] script: echo except: - schedules deploy: stage: deploy needs: ['test'] script: echo ``` 3. Create a daily pipeline schedule against the default branch under CI/CD > Schedules page 4. Await the schedule execution time, or attempt an immediate execution of the schedule 5. Schedule does not launch a pipeline 6. Intuitively head to CI/CD > Pipelines page to try to find why the schedule failed to run 7. No pipeline entry matching the schedule appears in CI/CD > Pipelines page 8. There's zero information _anywhere_ on the UI as to why the schedule failed to run ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change * Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements * If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html --> ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/ In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Is this a cross-stage feature? <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### Links / references ### Customer information - https://gitlab.zendesk.com/agent/tickets/161875 (internal) - https://gitlab.my.salesforce.com/00161000003SRl0AAG