Monitoring & debugging
Quick answer
Tracing, workflow case inspection, logging and common failure patterns when debugging SailPoint IdentityIQ workflows.
Key takeaways
- Inspect the WorkflowCase for variables, step and errors
- Enable trace and targeted logging to see execution
- Watch for stuck approvals and script exceptions
- Fix root causes, do not just clear stuck cases
Workflow cases
Every run creates a WorkflowCase you can inspect to see variables, the current step and any errors. It is the first place to look when something stalls.
Trace and logging
Enabling trace prints the step-by-step execution to the log. Targeted log4j settings on the workflow packages reveal script errors and transition decisions.
Common failures
Stuck approvals, unresolved approvers, script exceptions and provisioning-plan errors are the usual causes. Read the case and the log together.
Cleaning up
Terminate or restart stuck cases from the console, and fix the root cause (an approver rule or a script) rather than just clearing symptoms.
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
What object shows a running workflow’s state and errors?
- A. Identity Cube
- B. WorkflowCase
- C. Application
- D. Task result only
Show answer
B. WorkflowCase
The WorkflowCase holds variables, current step and errors for each run.