Hi @sup3rmark, I reported the problems with Okta rate limits triggered by the SailPoint connector in May 2024, due a lack of constraint to the multi-threading on the SailPoint side ( SailPoint’s Okta connector does not respect rate limits - Feedback / General Feedback - SailPoint Developer Community)
We have our Okta accounts federated with our parent’s EntraID tenant, so we don’t really need to go past of “PROVISIONING” state as users activate their accounts on their first login with their federated account.
However, whenever we modify some companywide roles, we have to pre-provision the group assignment in Okta, sync into SailPoint the change and then enable the role to avoid overloading our tenant due this “known issue”.
Unfortunately at this point working around SailPoint’s limitations is how we have been making progress because providing solutions to our problems doesn’t seem to be a priority for them.