Handling HTTP 429 Error in Connector: Increasing Request Interval?

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi everyone,

I’m encountering an issue with a connector in SailPoint while accessing an external company’s API. The exception I’m getting is:

bash

sailpoint.connector.ConnectorException: 
Url: https://app.customerfi.com/api/core/v1/companies/02de280e238f4b4cb710a87da55c57b0/users/52fec32774c64122a54557bba408d143/groups,
Message: 429 : Unknown Error,
HTTP Error Code: 429

As I understand it, the HTTP 429 error indicates “Too Many Requests,” meaning we’re hitting the rate limit set by the API.

I’d like to know:

  • Is there a way to configure the connector in SailPoint to increase the interval between API calls to avoid this error?
  • Are there any built-in features or best practices in SailPoint to manage request throttling or rate limiting effectively?
  • What strategies would you recommend to ensure smooth aggregation without overloading the API?

Thanks in advance for your help!

2

We encountered a similar issue when calling an endpoint to aggregate accounts, and we resolved it by adding a sleep timer to avoid exceeding the rate limit

3

Following a suggestion to resolve the HTTP 429 (Too Many Requests) error by adding a sleep timer, I’d like to ask for guidance on where exactly I should implement this in the connector ?

4

Hi @clebercarvalhoRaise, is this the Okta connector?

The failing endpoint looks very similar to Okta core apis and we’re suffering the same problem because SailPoint’s proprietary connector is unable to gracefully handle multi-threading.

SailPoint wasn’t able to provide any solution to our problem and I gave up chasing this. We just avoid doing major changes at the same time we sync Okta as eventually the sync happens anyway.

I love to know more details from @sunnyajmera on how we can insert “sleep timer” in our transactions as I lost hopes on a fix coming from SailPoint anyway.

Thanks!