---
sourceDocument: Brazil Telecommunications, Media, and Technology
sourceDocumentLink: https://www.servicenow.com/docs/r/telecom-media-technology

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Telecommunications, Media, and Technology

ft:clusterId :

    - telmt

bundleId :

    - telmt

workflow :

    - Customer and Industry


---

# Review applied consequences

# Review applied consequences {#ariaid-title1}

Release version: Brazil  
Updated October 13, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Check the action that was applied because of a violation and whether the action repeats.

## Before you begin

Role required: sn_st_mgmt.test_viewer

## About this task

An applied consequence is an action that was applied because of a threshold rule violation. It is created from a measure consequence that an administrator defined for the threshold rule. See [Define measure consequences for the threshold rules](https://www.servicenow.com/docs/WJlx6jNvQ7t3eZX95YybtQ "Set actions or responses to trigger when the test measure results fall outside the predefined acceptable limits.").

## Procedure

1. Navigate to AllService Test ManagementTest RunsAll.
2. Open the test run.
3. In the Test Measures related list, select the test measure that you want to see the violations.
4. In the Threshold Rule Violations related list, select the violation that you want to open.
5. In the Applied Consequences related list, select the applied consequence that you want to open.
6. Review the applied action and the repeat action option.
7. Check the measure consequence that the applied consequence came from.

## Result

Diagnostic tasks and resolution tasks help your teams investigate and fix the underlying problem. They're described in the Customer Service Problem Management documentation. See [Related Customer Service Problem Management information](https://www.servicenow.com/docs/FrjRqiis0DsPvFpIx1ePNw "Find the Service Test Management features that are described in the Customer Service Problem Management documentation.").

*[\>]: and then