Task
Quick answer
A Task is a unit of background work, aggregation, identity refresh, certification generation, run on a schedule or on demand.
Key takeaways
- What the Task object represents
- Key attributes and relationships
- How it is created and maintained
- Where it appears in governance
The Task object represents a unit of background work in IdentityIQ, a job that runs on a schedule or on demand rather than in the interactive UI. Aggregation, identity refresh, role propagation, certification generation and reports are all tasks. Understanding tasks is essential because they are where most heavy processing, and most operational troubleshooting, happens.
Common task types
- Account/identity aggregation, read data from sources.
- Identity refresh, recompute cubes, roles and policy.
- Role propagation, push role changes to members.
- Certification generation, build review campaigns.
- Reports and housekeeping.
Scheduling and partitioning
Tasks run on a schedule or manually and are executed by task/request servers. Heavy tasks can be partitioned, split into units of work distributed across threads and servers, which is the primary way to make large aggregations and refreshes finish in reasonable time.
Task results: your first diagnostic
Every task run produces a task result recording success, failure, counts and errors. When something governance-related looks wrong, a stale cube, missing access, a failed campaign, the relevant task result is almost always where the root cause is visible. Reading task results is a core operational skill.
Common pitfalls
- Unpartitioned heavy tasks that run for hours.
- Aggregation scheduled without a following refresh.
- Ignoring task-result errors until they compound.
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 is a Task?
- A. Failed tasks often reveal the root cause of governance issues.
- B. Aggregation, identity refresh, role propagation and certification generation.
- C. A scheduled or manual background job such as aggregation or refresh.
Show answer
C. A scheduled or manual background job such as aggregation or refresh.
A scheduled or manual background job such as aggregation or refresh.
Name common tasks.
- A. A scheduled or manual background job such as aggregation or refresh.
- B. Failed tasks often reveal the root cause of governance issues.
- C. Aggregation, identity refresh, role propagation and certification generation.
Show answer
C. Aggregation, identity refresh, role propagation and certification generation.
Aggregation, identity refresh, role propagation and certification generation.
Why check tasks when troubleshooting?
- A. A scheduled or manual background job such as aggregation or refresh.
- B. Aggregation, identity refresh, role propagation and certification generation.
- C. Failed tasks often reveal the root cause of governance issues.
Show answer
C. Failed tasks often reveal the root cause of governance issues.
Failed tasks often reveal the root cause of governance issues.