<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z000074tf5HCAQOkta Classic EngineAdministrationAnswered2021-07-22T09:49:43.000Z2021-07-21T07:46:58.000Z2021-07-22T09:49:43.000Z

AdamC.20484 (Customer) asked a question.

Production org has hit 60% rate limit for /sage/api/v1

One of our service delivery team did a search for a user and then downloaded the CSV file for this activity yesterday. This activity pushed our api limit above 60%. The target was a URL pattern. This is somewhat concerning for us as we have only just started using OKTA and this is our production instance. This was a single query. We are not sure what will happen when our customers make more calls on us for this information. Please advise.


This question is closed.
Loading
Production org has hit 60% rate limit for /sage/api/v1