Failures for github-tags lookups due to "API rate limit already exceeded for user ID 123456"

[chopeen]

How are you running Renovate?

Self-hosted Renovate

Which platform you running Renovate on?

GitLab (.com or self-hosted)

Which version of Renovate are you using?

42.39.2-full

Please tell us more about your question or problem

Over the last 2-3 weeks I have observed an increased number of errors Failed to look up github-tags package .... The poetry.lock files are also not getting updated (error No tool releases found).

The GitHub token is set and valid; it has worked fine for years and it has not expired. However, I generated a new personal access token (classic) to be sure. No change.

Are you aware of any changes to the GitHub API recently?

Have the API limits been lowered? Does the token need to be generated with certain scopes?

PS. There are surprising few hits for "API rate limit already exceeded for user ID" in Google results.

Logs (if relevant)

Logs

DEBUG: Datasource unknown error (repository=REDACTED-agentspoc)
       "datasource": "github-tags",
       "packageName": "antonbabenko/pre-commit-terraform",
       "err": {
         "message": "API rate limit already exceeded for user ID 123456.",
         "stack": "Error: API rate limit already exceeded for user ID 123456.\n    at GithubGraphqlDatasourceFetcher.doRawQuery (/usr/local/renovate/lib/util/github/graphql/datasource-fetcher.ts:135:21)\n    at processTicksAndRejections (node:internal/process/task_queues:103:5)\n    at GithubGraphqlDatasourceFetcher.doShrinkableQuery (/usr/local/renovate/lib/util/github/graphql/datasource-fetcher.ts:198:20)\n    at GithubGraphqlDatasourceFetcher.doPaginatedFetch (/usr/local/renovate/lib/util/github/graphql/datasource-fetcher.ts:247:27)\n    at GithubGraphqlDatasourceFetcher.doCachedQuery (/usr/local/renovate/lib/util/github/graphql/datasource-fetcher.ts:287:7)\n    at GithubGraphqlDatasourceFetcher.getItems (/usr/local/renovate/lib/util/github/graphql/datasource-fetcher.ts:325:17)\n    at GithubGraphqlDatasourceFetcher.query (/usr/local/renovate/lib/util/github/graphql/datasource-fetcher.ts:59:19)\n    at queryTags (/usr/local/renovate/lib/util/github/graphql/index.ts:15:15)\n    at GithubTagsDatasource.getReleases (/usr/local/renovate/lib/modules/datasource/github-tags/index.ts:81:24)\n    at getRegistryReleases (/usr/local/renovate/lib/modules/datasource/index.ts:89:15)\n    at huntRegistries (/usr/local/renovate/lib/modules/datasource/index.ts:144:13)\n    at fetchReleases (/usr/local/renovate/lib/modules/datasource/index.ts:369:15)\n    at lookupUpdates (/usr/local/renovate/lib/workers/repository/process/lookup/index.ts:158:56)\n    at /usr/local/renovate/lib/workers/repository/process/fetch.ts:81:12\n    at LookupStats.wrap (/usr/local/renovate/lib/util/stats.ts:39:20)\n    at /usr/local/renovate/lib/workers/repository/process/fetch.ts:133:23\n    at file:///usr/local/renovate/node_modules/.pnpm/[email protected]/node_modules/p-map/index.js:139:20"
       }
DEBUG: Failed to look up github-tags package antonbabenko/pre-commit-terraform (repository=REDACTED-agentspoc, packageFile=.pre-commit-config.yaml, dependency=antonbabenko/pre-commit-terraform)

[jamietanna]

Might be worth a support ticket with GitHub, as that sounds like the user the PAT is for is being personally rate limited

I think I've seen this before when i.e. I've got a GITHUB_COM_TOKEN associated with my personal user, then if I'm doing other API calls to GitHub, my whole user gets rate limited, if you hit a certain (large) number of API calls

Support should be able to help a little more 🤞

[chopeen]

I think this is the root cause:

1. The number of project monitored by the Renovate instance in question grew almost 50% this year
2. The number of concurrent jobs running Renovate was increased to support the growing number of projects to scan

Most likely this means that too many parallel requests are sent to the GitHub API, see rate-limits-and-query-limits-for-the-graphql-api#secondary-rate-limits.

The token is fine, the limits are unchanged, but the generated load increased and it started exceeding the limits.

[jamietanna]

Makes sense! Might be worth seeing if migrating from a User to a GitHub App may help you with rate limits - as you're self-hosting, I mean creating a new GitHub App for your org to use (there are other things to watch out for when migrating)