<!--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=420396) </details> <!--IssueSummary end--> GraphQL schema validations occur at least two points: 1. On a CI job which ensures that all the queries we package with the codebase used by the frontend are valid 2. When a query is sent to the GraphQL API, it is checked for validity. #396784 explors a problem in which `graphql_validation` was timing out on CI. This was fixed partially by overriding the default schema timeout in our CI jobs from 0.2s to 1s :point_right: !115443 But the schema validation on the API server is still 0.2s. The error shown here is a low-level GraphQL error from the framework (not our code) but we can control this by possibly bumping the `validate_timeout` value in `graphql/gitlab_schema.rb`.  See slack thread for relevant links (internal only, 90 days): https://gitlab.slack.com/archives/CETG54GQ0/p1690822374237289 Originally raised by @vkelkar :raised_hands: