Troubleshooting · LessonReviewed by Imran Q, SailPoint Trainer, 7 yrs · Updated · Published · IdentityIQ 8.4 · all levels
SailPoint Task failed
A scheduled task ended in a failed state.
Quick answer
A failed task reports its error in the task result. Causes range from database issues to rule errors to resource limits.
Key takeaways
- Symptom: A scheduled task ended in a failed state.
- Most likely causes
- Step-by-step fixes
- How to prevent recurrence
A scheduled task ended in a failed state, aggregation, refresh, certification generation, a report, or a custom task. Tasks are where heavy processing happens, so failures here often have a clear technical cause in the result.
Start here: read the evidence
Read the task result and its stack trace. This is the definitive record of what the task did and why it stopped, and it usually names the exact exception.
Likely causes, in order
- Database connectivity or timeout, the task could not reach or complete against the database.
- Rule error inside the task (a custom rule throwing).
- Resource limits, out-of-memory or thread exhaustion on a heavy job.
- Partition/worker failure in a partitioned task.
How to fix it
- Read the task result and stack trace.
- Check database health, connections and the connection pool.
- Review any custom rules the task invokes.
- Increase resources or partition the task if it is memory- or time-bound.
- Re-run and monitor to completion.
Preventing recurrence
Partition heavy tasks, size the JVM and connection pool for the workload, and alert on task failures so they are addressed before they cascade into stale data.
Common pitfalls
- Guessing instead of reading the task/transaction result, which usually names the cause.
- Fixing the symptom, not the root cause, so it returns.
- Changing several things at once, so you cannot tell what worked.
Want this with a live instructor and a lab tenant?