Problem Record detection automatically reviews new incidents to identify recurring issues before the weekly Landscape Intelligence analysis. It compares incident details across users and workgroups, and when the same issue appears repeatedly, it recommends creating a Problem Record so the support team can address the root cause instead of handling incidents individually.
It runs on a configurable schedule and builds clusters from incidents logged since the last run. This allows administrators to:
Detect and investigate issues earlier
Reduce duplicate incidents
Speed up problem management

Figure: Problem Records
Problem record suggestions are categorized as Detected or Confirmed based on whether the same incident theme continues to appear in subsequent pipeline executions.
Detected
A problem suggestion is classified as Detected when a recurring incident theme is identified for the first time during the latest analysis. These suggestions help IT administrators identify emerging issues that may require further investigation.
Figure: Detected
For example, if multiple incidents relate to the same underlying issue, Landscape Intelligence can identify the common theme and suggest it as a potential Problem record.
Confirmed
A problem suggestion is classified as Confirmed when the same incident theme is identified again during a subsequent pipeline execution. A recurring theme indicates that the issue continues to occur and may require formal Problem Management attention.
Figure: Confirmed
Example;
Assume multiple incidents are reported for users who are unable to access a website. Landscape Intelligence identifies the recurring pattern and suggests a Problem record based on the common issue. The first time the pattern is identified, the suggestion appears under Detected. If similar incidents continue to occur and the same pattern is identified during the next pipeline execution, the suggestion is classified as Confirmed. This allows administrators to distinguish between newly identified issues and recurring issues that require further investigation.
Problem Record Cluster Flow
.jpg?sv=2026-02-06&spr=https&st=2026-11-20T21%3A57%3A53Z&se=2026-11-20T22%3A08%3A53Z&sr=b&sp=r&sig=tfZ9J6Unma9bhnk3RxUGRfJA4M2ZdcnZWK69v6yCWwc%3D)
Notes
Instead of treating five Outlook incidents as separate tickets, the system recognizes they are related and recommends a single Problem Record to address the underlying issue.
The execution schedule is configured in UTC. Adjust the scheduled time according to your local time zone.