t106d (t106d) asked a question.
Hello Okta Community,
I am currently facing an issue with a bulk user import process using Okta Workflows. According to the documentation, it is possible to import up to 10,000 users per session. However, during the import process, the workflow consistently stops after processing 50 records.
We are importing users into a custom source app, and we have over 70,000 users to import. Importing them 50 users at a time will take an excessive amount of time and is not feasible for our needs.
Has anyone else encountered this issue? If so, how did you resolve it? Are there any specific configurations or workarounds that could allow us to import all users without stopping at 50? Any help or advice would be greatly appreciated!
Thank you in advance for your assistance!
Hello @t106d (t106d) Thank you for posting on our Community page!
I have checked our documentation and I was unable to find anything in regards to your issue. I would recommend to open a case with Support to further investigare this issue and see if this a problem with the configuration or bug.
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Ask Us Anything thru 9/3 Okta’s New MFA Requirement for Admin Console Access
@t106d (t106d) -- First thing to keep in mind that Okta Workflows is a client. It isn't directly part of XaaS. As a scriptable client it allows you to automate the construction of payloads that can be sent to XaaS.
As far as XaaS goes:
https://help.okta.com/en-us/content/topics/users-groups-profiles/usgp-anything-as-a-source.htm
A batch is going to be an Array(List) of users. So you will batch send 200 (50) times for a total of 10k maximum in a single import.
The following Blog post should give you some insight on how to build out the batches using Workflows:
https://iamse.blog/2023/06/01/okta-workflows-how-to-anything-as-a-source-with-pagination/