Investigate root cause of a problem
- UpdatedJul 31, 2025
- 2 minutes to read
- Zurich
- Problem Management
Identify the root cause of the problem to analyze, track, and resolve recurring incidents permanently.
Before you begin
Role required: problem_admin, problem_coordinator, problem_manager, or admin
About this task
Activate the Problem Management Best Practice — Madrid — State Model (com.snc.best_practice.problem.madrid.state_model) to get the new best practice states and guided actions to navigate the life cycle of a problem. For details, see Activate Problem Management Best Practice — Madrid — State Model.
Procedure
| Option | Actions to be taken |
|---|---|
| Investigate the problem |
For more information about creating a problem task, see Create a problem task. |
| If you can resolve the problem | Click Fix. The problem state changes to
Fix in Progress. You can then create a new
Change Request or link to an existing Change Request to apply a
permanent fix to the problem. Note: Notification is sent to the problem
coordinator, who is assigned to the Problem, when all the related
Change Requests are completed or canceled.
|
| If you acknowledge the problem but there is no permanent resolution to the problem | Click Accept Risk. The problem directly
enters the Closed or
Resolved state with the Resolution
code as Risk
accepted. Note: Whether the problem enters the
Closed state or the
Resolved state, depends on the property
Accept Risk moves the Problem to Closed state instead
of Resolved state
(problem.acceptrisk.move_to_closed).
|
| If you decide to reanalyze the problem | Click Re-analyze. The problem opens for reanalysis and the state is changed to Root Cause Analysis. |
What to do next
You can resolve and complete the problem. You can also create a change request to implement a fix for the problem.