Study guide
15.2 Leveraging the Administrator Console for Debugging
SailPoint Certified IdentityIQ Engineer Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: The IdentityIQ Engineer Exam
1.1 Exam Format, Official Blueprint, and Study Strategy
2 Chapter 2: Infrastructure, Installation, and Extended Attributes
2.1 IdentityIQ Infrastructure Components 2.2 Installation Steps and Procedures 2.3 Creating Extended Attributes and the Objects That Support Them
3 Chapter 3: Build, Deployment, Patching, Access, and Email
3.1 Ongoing Build and Deployment 3.2 Installing Patches and Performing Upgrades 3.3 Configuring End-User Access 3.4 Email Server Settings and Email Redirection
4 Chapter 4: Lifecycle Manager Configuration, Provisioning Policies, and Workflows
4.1 Configuring Lifecycle Manager 4.2 Identity Provisioning Policies 4.3 Configuring LCM Workflows
5 Chapter 5: Lifecycle Events, QuickLinks, Batch Requests, and Rapid Setup
5.1 Lifecycle Events and Their Workflows 5.2 QuickLinks and QuickLink Populations 5.3 Configuring and Using Batch Requests 5.4 Rapid Setup in Lifecycle Events and Identity Operations
6 Chapter 6: Certification Campaigns and Certification Rules
6.1 Configuring and Scheduling Certification Campaigns 6.2 The Purpose of Common Certification Rules
7 Chapter 7: Policies and Policy Violations
7.1 Configuring and Leveraging Policies 7.2 Responding to Policy Violations
8 Chapter 8: Reporting, Advanced Analytics, and Auditing
8.1 Executing and Leveraging Reports 8.2 Leveraging Advanced Analytics 8.3 Configuring and Using Auditing
9 Chapter 9: Rules, Rule Libraries, and the SailPoint API
9.1 The Purpose and Use of Rule Libraries 9.2 Rule Input and Output Arguments 9.3 Common SailPoint API Objects and Methods
10 Chapter 10: Workflow Development
10.1 Workflow Variables, Transitions, and Step Conditions 10.2 Workflow Steps That Generate Work Items 10.3 The Different Workflow Step Usages 10.4 Leveraging Sub-Workflows
11 Chapter 11: Email Templates, Branding, and Localization
11.1 Customizing and Using Email Templates 11.2 Branding the SailPoint User Interface 11.3 Localizing the SailPoint UI
12 Chapter 12: Application Definitions, Connector Settings, and Rapid Setup Aggregation
12.1 Configuring Application Definitions 12.2 Configuring Common Connector Settings 12.3 Configuring Rapid Setup Aggregation Settings
13 Chapter 13: Data-Loading Tasks and Application and Connector Rules
13.1 Scheduling Tasks for Data Loading and Processing 13.2 Common Application Rule Types 13.3 Common Connector Rule Types
14 Chapter 14: Debugging with log4j, Syslog, and the IdentityIQ Console
14.1 Configuring and Leveraging log4j 14.2 Configuring and Leveraging Syslog 14.3 Leveraging the IdentityIQ Console for Debugging
15 Chapter 15: Debug Pages and the Administrator Console
15.1 Leveraging the Debug Pages for Debugging 15.2 Leveraging the Administrator Console for Debugging
16 Chapter 16: Role Model and Identity Attribute Mappings
16.1 Default Role Models and Role Types 16.2 Configuring Roles and Role Options 16.3 Configuring Identity Attribute Mappings
17 Chapter 17: Data Objects, Relationships, and Group Types
17.1 Common IdentityIQ Data Objects 17.2 Relationships Between Common Data Object Models 17.3 The Difference Between Group Types
15.2 Leveraging the Administrator Console for Debugging
Key Takeaways Explain This Topic AI
The Administrator Console has Tasks, Provisioning, and Environment areas, and access to it is controlled by IdentityIQ rights separate from the Setup > Tasks page.
From the Active tab you can terminate a running task or request a stack trace; from the Scheduled tab you can postpone a task or delete a schedule.
The Provisioning Transactions table logs only failures by default; set the Maximum Log Level to Retry or Success for more, and set a deletion age so the table does not grow forever.
Pending (retryable) transactions can be retried immediately; permanent failures cannot be retried but can be overridden with a manual work item.
Environment shows host heartbeats and statistics, lets you switch services per host, and runs application health checks from chosen hosts.
Last updated: September 2026
Leveraging the Administrator Console for Debugging
Objective 6.6 asks you to leverage the Administrator Console for debugging . Open gear icon > Administrator Console . It has three areas: Tasks , Provisioning , and Environment . Access is controlled by IdentityIQ rights , so someone may have the Administrator Console without the Setup > Tasks pages, or the reverse.
Tasks: What Is Running, Scheduled, and Done
Tab Columns Actions
Active Name, type, start date, owner, host , current runtime , average runtime Terminate (X), and request a stack trace ( </> turns green when ready; you can request a new one)
Scheduled Name, type, host, next and last execution, last result, owner Postpone to a chosen date and time, or delete the schedule
Completed Result, start and complete dates, host, runtime, Diff from Average Review outcomes
Key behaviors:
Terminate sends a request that out-of-the-box tasks honor at their next logical breakpoint. Custom tasks should also be written to handle a terminate request. You can also terminate from Setup > Tasks > Task Results .
Stack traces show what a long-running task is doing right now. They do not apply to workflows , which also produce task results, so the button is disabled for them.
Postpone blocks every instance of the task until the chosen time. Afterward, the task resumes its normal schedule . It does not run immediately at that time.
Average runtime and Diff from Average show when a task is slower than usual, an early sign of data growth, a slow target, or a database problem.
Provisioning: Every Change That Went to a Target
The Provisioning Transactions table records provisioning through connectors , manual work items , and IdentityIQ operations . Its tabs are All , Failure , Success , and Pending (retry).
Controlling What Is Logged
On Global Settings > IdentityIQ Configuration > Miscellaneous > Provisioning Transaction Log Settings :
Enable Provisioning Transaction Log turns logging on or off.
Maximum Log Level : Failure (the default, only failures set up for retry), Retry (failures and retry results), or Success (everything).
Days before provisioning transaction event deletion : 0 means never delete . With Success logging this can fill the database quickly, so always set a retention period. The Perform Maintenance task's Prune provisioning transactions option uses it.
Acting on Transactions
The information icon opens Transaction Details , with attribute-level request data and error messages. This is usually the fastest route to the cause of a failed provisioning.
Pending transactions (retryable errors) retry automatically after a configured interval. An administrator can click Retry to force an immediate retry, for example once a network problem is fixed.
Failure transactions are permanent . They are never retried automatically and cannot be forced to retry . Instead, Override creates a manual work item assigned to the application owner, yourself, or another user, to complete the change outside IdentityIQ. The original failure stays for history, and a new Success entry records the override.
The report button launches the Provisioning Transaction Object report. The Provisioning Transaction Object and Detailed Provisioning Transaction Object reports are also on Intelligence > Reports.
Environment: Hosts, Applications, Modules
Hosts tab. Every IdentityIQ instance, with Status , Last Heartbeat , CPU , memory , request threads , task threads , database response time , and timestamp . A host whose heartbeat stops advancing is marked crashed by the others. Actions per host:
Services tab turns host services on or off: Task, Request (never fully off), Monitoring, Reanimator (recovers or terminates hung tasks), and others (section 2.1).
Configuration tab overrides polling interval, statistics retention, and which statistics are kept, and selects applications to monitor from this host.
Delete a host's Server object. It reappears at the next heartbeat if the server is still running.
Global defaults (polling interval, retention, statistics) are set with the gear on the title bar.
Applications tab. Monitored applications show how many hosts see them up or down , with the last ping . With full rights, you can trigger an immediate health check with the refresh icon. An application must be monitored by at least one host before it reports.
SailPoint Modules and Extensions tab. Installed modules and extensions, their statuses, last ping, and a Problem Detected icon with details.
Administrator Console vs. Other Tools
Task Results (Setup > Tasks) shows task outcomes with full result details and can also terminate tasks. Postponing schedules and requesting stack traces are done in the Administrator Console, which has its own access rights.
Syslog (section 14.2) holds the exceptions behind many failures. The console shows that something failed, and Syslog and logs show why .
Debug pages > Threads give a server-wide thread dump, while the console's stack trace targets one running task.
Debugging Playbook
Symptom Administrator Console step
The nightly refresh is still running at 9 a.m. Active tab: compare with the average runtime, request a stack trace , and terminate if necessary
Users report access was "approved but never granted" Provisioning: filter Failure or Pending and open Transaction Details
A target system was down for an hour Provisioning: after recovery, Retry the Pending items
Partitioned tasks slow down Environment: check hosts' request threads , heartbeats, and whether a host has dropped out