Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.
This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

To process 2000+ Update User tasks, WSRETRYJOB had to be run multiple times instead of once

yusufw
New Contributor III
New Contributor III

‎05/16/2023 11:38 AM

After running an import job, over 2000+ User Update tasks were created, to update users in the HR system, SAP SuccessFactors.
There is a Provisioning Job (WSRETRYJOB) that was created to process these tasks.

When we started the WSRETRYJOB the first time, it processed and completed over 500+ tasks and then stopped.
We ran it a 2nd time, and it completed another 1000+ tasks, then stopped.
Then we ran the job a 3rd time, for it to process the rest of the tasks.

How can the job be configured so that it processes all of the tasks on the first run?
Is there some limitation on how many tasks could be processed?

The concern is that when the task is used in Production, it wouldn't be able to process the 1000s of User Update tasks that are anticipated in a single execution.

Labels:
0 Kudos
1 REPLY 1

Sivagami
Valued Contributor
Valued Contributor

‎05/16/2023 01:05 PM

There are 2 places you can configure provisioning limits.

1) Check the provisioning limit configuration in Security System - https://docs.saviyntcloud.com/bundle/SSM-Admin-v55x/page/Content/Chapter04-Onboarding-and-Managing-A... 

Provisioning limit contains the list of task types that are generated and enables you to specify the Provisioning Limit count. After the Security system is created, click Edit to update the provisioning limit for all the Task Types. The provisioning limit count specified processes the respective number of tasks when WSRETRY job runs each time. The tasks exceeding the specified provisioning limit are displayed as an error in the Other Details section of the WSRETRY Job specifying the reason why it was not processed. The next time when WSRETRY job schedule is run, the unprocessed tasks are completed again based on the count limit specified.

For example, for a CHANGEPASSWORD task if provisioning limit is specified as 2 and if there are 5 pending tasks then when WSRETRY runs for 1st time, it processed 2 change password tasks and shows error for the remaining 3. The 2nd time, WSRETRY runs it processes the remaining 2 and gives error for remaining 1. The 3rd time when it runs, it completes the remaining 1 task.

Below are the various task types that are generated from either: import, rules, requests, bulk update, REST API, user being added to Role, and for other features from wherever tasks are being generated.

  • ADD: Allows you to specify the provisioning limit for: add user, add access, and add account. 

  • UPDATEUSER: Allows you to specify the provisioning limit for update user task. The tasks for this are generated from: User update rule, ARS > update user tile. 

  • CHANGEPASSWORD: Allows you to specify the provisioning limit for ChangePassword task. The Change password task is generated from ARS > Change Password tile.

  • DISABLEACCOUNT: Allows you to specify the provisioning limit for Disable Account task. The Disable account task is generated from user update rule.

  • DELETEACCOUNT: Allows you to specify the provisioning limit for Delete Account task. The Delete account task is generated from: rules, ARS.

  • DEL: Allows you to specify the provisioning limit for Delete task. 

  • UPDATEACCOUNT: Allows you to specify the provisioning limit for Update Account task. The Update Account task is generated from: ARS, user update rule, and schema import.

  • PROPOSEDACCOUNTOWNERS: 

  • PROPOSEDENTOWNERS:

  • NEWROLEREQUEST: Allows you to specify the provisioning limit for New Role Request task. The Update Account task is generated from ARS. 

  • ENABLEACCOUNT: Allows you to specify the provisioning limit for Enable Account task. The Enable Account task is generated from user update rule.

  • NEWACCOUNT: Allows you to specify the provisioning limit for New Account task. The New Account task is generated from: ARS, Rules, and Roles. 

  • MODIFYPRIVILEGE: Allows you to specify the provisioning limit for Modify Privilege task. The Modify Privilege task is generated from ARS.

2) ConfigJson in Connections - https://docs.saviyntcloud.com/bundle/REST-v2020x/page/Content/Configuring-Provisioning-Tasks-and-Con... 

Review these configs and set appropriate limits for the tasks to go through in one run.

-Siva

Copyright © 2024 Khoros, LLC