Troubleshooting hub
Quick answer
Most IdentityIQ issues fall into a few buckets: connection and IQService failures, correlation gaps producing orphans, provisioning errors from bad plans or target rules, and workflows stuck on approvals. Read the task result, then the application and workflow logs, and work from the error, not a guess.
Key takeaways
- Start from the task result and logs, not guesses
- Connection/IQService issues stop aggregation and provisioning
- Correlation gaps create orphan accounts
- Provisioning fails on bad plans or target constraints
- Stuck workflows are usually pending approvals
The troubleshooting module is where enterprise search traffic and real operational value meet: it documents the specific failures teams actually hit in production, provisioning failures, connector timeouts, aggregation and refresh errors, stuck workflows, failed tasks and certifications, and performance problems, with methodical diagnosis and fixes.
What this module covers
Each page follows the same discipline: read the evidence (task or transaction result), work through the likely causes in order, apply the fix, and prevent recurrence. This reflects how experienced practitioners actually debug SailPoint.
What you will find here
- Provisioning failed and connector timeout.
- Aggregation failed and identity refresh failed.
- Workflow stuck, task failed, certification failed.
- Performance issues.
How to use it
When something breaks, go to the page for that symptom, start with the evidence it points you to, and work down the ordered list of causes rather than guessing. Fix the root cause, not just the symptom.
Common pitfalls
- Guessing instead of reading the task/transaction result.
- Fixing symptoms rather than root causes.
- Changing several things at once so you cannot tell what worked.
Want to learn this properly?
Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.
Check your understanding
The first place to look for a failure is the?
- A. Task result and logs. Task results and logs usually name the exact failure.
- B. Waiting on an approval. Workflows commonly stall on a pending approval or failed step.
- C. Correlation problem. Missing or wrong correlation attributes create orphans.
Show answer
A. Task result and logs. Task results and logs usually name the exact failure.
Task result and logs. Task results and logs usually name the exact failure.
Orphan accounts are almost always a?
- A. Correlation problem. Missing or wrong correlation attributes create orphans.
- B. Task result and logs. Task results and logs usually name the exact failure.
- C. Waiting on an approval. Workflows commonly stall on a pending approval or failed step.
Show answer
A. Correlation problem. Missing or wrong correlation attributes create orphans.
Correlation problem. Missing or wrong correlation attributes create orphans.
A stuck workflow is most often?
- A. Correlation problem. Missing or wrong correlation attributes create orphans.
- B. Task result and logs. Task results and logs usually name the exact failure.
- C. Waiting on an approval. Workflows commonly stall on a pending approval or failed step.
Show answer
C. Waiting on an approval. Workflows commonly stall on a pending approval or failed step.
Waiting on an approval. Workflows commonly stall on a pending approval or failed step.