What is a one sentence summary of your feature request?
The Threshold limits should not encompass both syncing and provisioning activities
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Currently, there appears to only be one threshold limit that can be set for both syncing and provisioning events. The problem is that if we are just reading in changes from Active Directory and it exceeds the threshold, then it holds up our full sync job. We would raise the threshold limit, but would only want to raise it for sync (read-in) events, and not for provisioning (write-out) events. As you can see from the attached screenshot, we read in 1000+ AD changes, which is ok. We don’t care about this many reads, but would definitely want to review if there were this many write-outs to a target system like AD.
How do you currently solve the challenges you have by not having this feature?
We don’t. We sometimes don’t realize that the sync job has been held up until several hours later, and this can be a bigger issue on the weekends, when we may have terminations that need to be triggered and completed to remain compliant with our auditors.
