Diagnosing Provisioning Errors and Retries
Key Takeaways
Use Account Activity details, the Provisioning Activity report and manual tasks to identify the operation and error.
Documented retryable provisioning errors include ConnectException and NoRouteToHostException.
Retryable provisioning is scheduled hourly for up to three retries. Queue load can delay execution.
Inspect the target for partial success before resubmitting account creation.
Locate the failed stage
Collect the requester or initiating process, recipient, source, account, expected operation and incident time. Inspect Admin > Identity Management > Activities and open the relevant item in Account Activity. The entry distinguishes status and stage. Its details can show errors for the underlying operation. Use the Provisioning Activity report under Search reports for individual provisioning events. For work performed by people, inspect Admin > Dashboard > Tasks. Verify which account and action the task names and who is responsible for it.
Classify the first stage for which evidence is missing. Confirm the request has the required approvals, or verify that the role or lifecycle trigger applied. For automated writes, confirm the connector got an operation for the intended source account. Use the error and target evidence to distinguish credential or network faults, unsupported operations, data validation, and authorization. A working aggregation proves the source can perform a read. Check write permissions and the actual provisioning route separately.
| Symptom | Next evidence |
|---|---|
| Request looks approved, but no completed target change | Activity stage, pending work items and the recipient/source selected |
| One automated profile assignment fails for an identity with multiple accounts | Selection criteria, candidate count, and any manual account-selection task |
| Retryable connection exception | Connector path, latest retry status and time, actual source state |
| Target reports a missing or invalid attribute | Evaluated policy field, mapped value, target contract and account state |
| Flat-file source with outstanding work | Assigned task, expected manual operation and evidence of target completion |
Evaluate retries in context
SailPoint documents connector errors such as ConnectException and NoRouteToHostException as examples of retryable provisioning errors. It schedules a retry after an hour and continues once per hour for up to three retries, with possible queue delay. For example, if an error at 09:20 is classified as retryable, the first retry is scheduled for about 10:20. Inspect the activity to see whether it actually ran. When a network path is restored before the next queued attempt, follow the recorded operation to completion and verify the native result before introducing another request. A field rejected by the target for an invalid value calls for diagnosing and fixing that input. For example, if the target reports a missing required account identifier and the evaluated plan lacks that field, work back to the relevant policy or identity input. A network change would leave that same request invalid. For escalation, record the exact failing operation and timestamps and remove credentials or unrelated personal data from diagnostic extracts.
A lifecycle account action such as disabling an account runs at the state transition. Lifecycle provisioning has the documented retry mechanism for retryable errors, but the transition is a poor substitute for an ongoing reconciliation process. If the account is manually re-enabled later while the lifecycle state stays the same, investigate the native state change and available remediation. Do not assume the unchanged lifecycle state launches a fresh disable on every refresh. Attribute Sync has separate retry behavior for failed synchronization, so read that feature’s limits for a sync incident.
Work a partial create
SailPoint documents an Active Directory error where a Create Account operation reports an IQService failure updating attributes, although the directory entry already exists. If the provisioning request includes manager, inspect whether its value is a manager’s distinguished name (DN) instead of a person’s display name. Confirm the account actually exists, determine which attributes are absent, and correct the mapping or native data through the approved remediation. A duplicate create can collide with the entry already present. The Active Directory connector also has a rollback option for failures of one or more required attributes. Check the configuration and observed target state instead of assuming it applies to every error.
You can close the investigation once the correct native account has the intended fields and access, the relevant transaction or manual work is reconciled, and any follow-up failure is identifiable. If needed, aggregate the affected account using the connector’s supported method to refresh the tenant view. Preserve the original and follow-up activity records. That allows the team to distinguish a corrected operation from a disappearance of an error message.
See SailPoint’s monitoring, retry behavior, lifecycle actions, Active Directory troubleshooting, and the connector’s provisioning settings.
At 09:20 a write fails with a connector error already classified by SailPoint as retryable. Which is the documented schedule?
Repeated attempts every minute until the identity changes state
An immediate retry followed by unlimited automatic attempts
No retry for connector connectivity errors
The first retry is scheduled about an hour later, up to three retries, subject to queue delays
Active Directory Create Account reports failure while setting the manager attribute. The new user’s directory entry exists. What should the engineer check before another write?
Whether the plan sent the manager’s distinguished name and which attributes are already present on the native account
Whether a second create with a new account ID will hide the failure
Whether scheduled identity processing can purge all access history
Whether the requester can add a second approval step to change the directory format
Sections you finish are checked off in the contents.