Job Service idle - v8.0

Have seen this again with a Adhodsync

We have a process which triggers an adhoc sync based on an update to a person object -> I did a bulk update of 5000 persons which triggered 5000 of these processes. At most, 5 adhoc sync jobs run in parallel, others are queued up and the server is only 10% CPU and memory utilized. Is there any way to get this service to pickup as many sync jobs in parallel as the external slots allow?

Each task or process component has a Max. instances parameter that controls how many jobs are executed concurrently. Please check the documentation https://support.oneidentity.com/technical-documents/identity-manager/8.0/configuration-guide/77#TOPIC-862590

Please keep in mind, that increasing this number for the AdHocProjection task, requires more memory on the job service executing these process steps.

Thank you Markus, awesome as always!

Markus Weiss-Ehlers - one more question, do we need to restart the job services if we change maxinstance either on component or task levl? Also, what does Process Function mean in this statement?

NOTE: The value is only used if the maximum number of instances of a process function is set to "0". Otherwise, the value applies that is set for the process task.

Process function does mean process task in this context. See the explanation of the max. instance value at the process task for reference.

You do not need to restart the JobService but the process steps that are already present in the job queue contain the old value.

Process function does mean process task in this context. See the explanation of the max. instance value at the process task for reference.

You do not need to restart the JobService but the process steps that are already present in the job queue contain the old value.