What is gitlab.com(not self-hosted) rate limit reset?

How to Use GitLab
,
1

Attempted research below.
How fast will the ratelimit be reset after being triggered? Is it the limit denominator? i.e. /v4/projects 2000 requests per 10min, means if my service account trips over 2000 requests everyone in the company will be blocked from making requests for 10min?

Does anyone have experience with how gitlab.com is handled compared to the Self-Hosted rate limiting reset? I could find no explicit mention or even suggestive example.

WHY?
I am trying to do my due diligence for potential impact of an API crawler we will use against our gitlab.com account. I have heavy rate limiting in place with testing, but stuff can always break in surprising ways, so I need to provide a potential impact and remediation plan.

RESEARCH
I have found plenty of documentation mentions under “Gitlab Self-Managed” where the reset will be one minute when the rate is “per minute” but:

  1. I could find no examples for “per 10 minutes” or similarly larger than one.
  2. No explicit statements or examples for how gitlab.com handles reset

I really should have been able to find this information in one of these documents/thread.

2

It’s found on your second link: GitLab.com settings | GitLab in particular this part:

and:

And then this link:

which should give response headers with such information. It does say it may or may not give those details though, so you may have to check it. From the page:

and:

so from Gitlab.com it should give you an idea of when you can retry. Since the admin panel is only accessible for self-managed, that part of the docs can be ignored since you won’t be able to change any values. But the rate-limit response header still applies, whether it’s self managed or SaaS (gitlab.com) and should tell you when you can retry.

With the response from the headers, you can then script to read that value and wait I guess that particular amount of time before retrying.