Task
The Task object: a scheduled or manual job like aggregation or refresh.
A Task is a unit of background work, aggregation, identity refresh, certification generation, run on a schedule or on demand.
- 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.