Check the job queue
Diagnostic Agent
Root cause analysis for One Identity. In minutes instead of hours.
The Diagnostic Agent automatically analyses technical relationships and delivers a structured diagnostic report with root-cause analysis, evidence, confidence score and concrete recommendations.
Instead of manual troubleshooting, you get a clear assessment of where the issue originates and what to do next.
The result is a structured report with root-cause analysis, evidence, confidence score and concrete recommendations.
0.94confidence score in the sample case
7+data sources analysed in parallel
Minutesinstead of hours of manual review
The problem
When a job freezes, the search usually begins.
A process gets stuck and the investigation starts:
The more complex the environment, the longer the search for the cause. In many cases the relevant information already exists, but is spread across tables, processes and configurations.
Search scripts
Analyse process chains
Compare database objects
Ask colleagues
The solution
The Diagnostic Agent works like an experienced One Identity consultant.
The agent analyses multiple sources at the same time and evaluates processes, configurations and dependencies in context.
Possible causes are assessed, unlikely scenarios are actively ruled out and the relevant evidence is assembled into a structured report.
The result is not a list of log lines, but a well-founded assessment of the most likely cause.
Evaluated sources
Job queue
Job chains
Dialog scripts
Person objects
IT shop structures
Historical data
Knowledge sources
The result
More than an error report.
The Diagnostic Agent provides a clear assessment of the problem and possible solution paths.
A clear summary of the cause in plain language, not just an error code
Prioritised recommendations: priority 1, 2, 3
Severity level: low / medium / high
Confidence score: how certain is the diagnosis?
Complete evidence: which data sources were evaluated and what do they show?
Documented exclusion criteria: why were other causes ruled out?
Instead of “Job Frozen”, you get a clear explanation with a concrete next step.
Case study
A practical example
Starting point
An automatic request for AD administrator rights got stuck in the IT shop.
The process did not complete and the reason was not immediately obvious. At first glance, nothing pointed to a technical error.
Analysis result
The Diagnostic Agent analysed the involved processes, permissions and configuration objects.
The cause was neither the script nor the job execution.
The affected identity was not assigned to the required customer node of the target shop. One Identity therefore blocked the request correctly.
Recommended action
Assign the identity to the correct customer node of the target shop before running the request again.