Content creation rate limits

  • Tier: Free, Premium, Ultimate
  • Offering: GitLab Self-Managed

Rate limits control the pace at which users can create issues, epics, notes, and merge requests, and resolve or unresolve threads.

Issue and epic creation

The limit for epic creation is the same limit applied to issue creation.

Prerequisites:

  • Administrator access.

To limit the number of requests made to the issue and epic creation endpoints:

  1. In the upper-right corner, select Admin.
  2. In the left sidebar, select Settings > Network.
  3. Expand Issues Rate Limits.
  4. Under Max requests per minute, enter the new value.
  5. Select Save changes.

The rate limit:

  • Is applied independently per project and per user.
  • Is not applied per IP address.
  • Is disabled by default.
  • Can be set to 0 to disable the rate limit.

Requests over the rate limit are logged into the auth.log file.

For example, if you set the limit to 300, requests that exceed a rate of 300 per minute are blocked. Access to the endpoint is available after one minute.

Note creation

You can configure the rate limit for requests to the note creation endpoint.

Prerequisites:

  • Administrator access.

To change the note creation rate limit:

  1. In the upper-right corner, select Admin.
  2. In the left sidebar, select Settings > Network.
  3. Expand Notes rate limit.
  4. In the Maximum requests per minute box, enter the new value.
  5. Optional. In the Users to exclude from the rate limit box, list users allowed to exceed the limit.
  6. Select Save changes.

The rate limit:

  • Is applied independently per user.
  • Is not applied per IP address.
  • Defaults to 300.
  • Counts each comment published from a review, including reviews submitted with the /submit_review or /approve quick action.

Users that you list in Users to exclude from the rate limit are also excluded from the note edit rate limit.

Requests over the rate limit are logged into the auth.log file.

For example, if you set the limit to 300, requests that exceed a rate of 300 per minute are blocked. Access to the endpoint is available after one minute.

Comments created by email and chat commands

The availability of this feature is controlled by a feature flag. For more information, see the history.

The note creation rate limit also applies to comments created by email and with Slack or Mattermost slash commands.

Service Desk replies are counted separately for each sender email address in each project. The Users to exclude from the rate limit setting does not apply to them.

When a comment sent by email is over the rate limit, GitLab does not create it and sends a rejection email to the sender. Each sender gets at most one of these rejection emails per minute.

Draft note creation

You can configure the rate limit for requests that create a draft note on a merge request. The limit applies to the UI and the REST API. Publishing draft notes counts against the note creation rate limit instead.

Prerequisites:

  • Administrator access.

To change the draft note creation rate limit:

  1. In the upper-right corner, select Admin.
  2. In the left sidebar, select Settings > Network.
  3. Expand Notes rate limits.
  4. In the Maximum draft note requests per minute box, enter the new value.
  5. Select Save changes.

The rate limit:

  • Is applied independently per user.
  • Defaults to 0, which disables the rate limit. On GitLab.com, the limit is 300.
  • Does not apply to users in the Users to exclude from the rate limit box for note creation.

Requests over the rate limit return 429 Too Many Requests.

Thread resolution

You can configure the rate limit for requests that resolve or unresolve a thread or a comment. The limit applies to the UI, the REST API, and the GraphQL API.

Prerequisites:

  • Administrator access.

To change the thread resolution rate limit:

  1. In the upper-right corner, select Admin.
  2. In the left sidebar, select Settings > Network.
  3. Expand Thread resolution rate limits.
  4. In the Maximum requests per minute box, enter the new value.
  5. Select Save changes.

The rate limit:

  • Is applied independently per user.
  • Is not applied per IP address.
  • Defaults to 120.
  • Can be set to 0 to disable the rate limit.
  • Counts each resolve or unresolve request, including requests for a thread that is already resolved or unresolved. A GraphQL request with multiple mutations counts each mutation. When a GraphQL request exceeds the limit, the whole request returns an error, but the mutations that ran before the limit was reached are not reverted.

Requests over the rate limit return 429 Too Many Requests.

Merge request creation

You can configure the rate limit for merge request creation. The limit applies to the UI, the REST API, the GraphQL API, Git push options, merge requests created from an issue, and merge requests created by email.

Prerequisites:

  • Administrator access.

To change the merge request creation rate limit:

  1. In the upper-right corner, select Admin.
  2. In the left sidebar, select Settings > Network.
  3. Expand Merge request creation rate limits.
  4. In the Maximum requests per minute box, enter the new value.
  5. Select Save changes.

The rate limit:

  • Is applied independently per user.
  • Is not applied per IP address.
  • Defaults to 0, which disables the rate limit. On GitLab.com, the limit is 150.

Requests over the rate limit return 429 Too Many Requests.