GraphQL query using API and pagination is receiving an HTTP status of 503

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

Users face 503 timeout errors when fetching for pipelines in all projects within the group including subgroups. This occurs even if the restricting the result to the first project.

Steps to reproduce

Execute the following GraphQL query.

query oldPipelineRuns($after:String=null, $afterTime:Time!, $beforeTime:Time!) {
 group(fullPath: "[top_level_group]")   {
   projects(first: 1, includeSubgroups: true, after:$after)
   {
     pageInfo
     {
       startCursor
       hasNextPage
       endCursor
     }
     nodes
     {
       id,
       fullPath,
       pipelines(updatedAfter:$afterTime, updatedBefore:$beforeTime)
       {
         nodes
         {
           id,
           project { fullPath },
           status,
           createdAt,
           finishedAt
         }
       }
     }
   }
 }
}

Example Project

What is the current bug behavior?

503 timeouts occur instead of providing the list of pipelines. The query was successful before, and started failing recently.

What is the expected correct behavior?

User should be shown the pipelines of the projects

Relevant logs and/or screenshots

Logs: https://log.gprd.gitlab.net/app/r/s/WImpH

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:env:info\\\`) (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:check SANITIZE=true\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\`) (we will only investigate if the tests are passing)

Possible fixes