# Scheme Rule Executions

The Scheme Rule Executions page helps users review the execution results of individual rules within a Data Quality Scheme. It enables stewards and administrators to investigate failures, analyze rule performance, and understand detailed data quality outcomes for each rule run.

Each row represents one rule execution performed as part of a scheme run. Users can search, filter, sort, export records, inspect failed values, and open the related Scheme Execution Summary for additional run details.

This page is useful for identifying which specific rules are failing, how many rows are impacted, and where remediation attention is required.

<figure><img src="/files/dXydtpjEojsKejZSnbp3" alt=""><figcaption></figcaption></figure>

### Execution List View

The Execution List View displays detailed results for each rule execution associated with the selected scheme.

<table><thead><tr><th width="192.6666259765625">Field</th><th>Description</th></tr></thead><tbody><tr><td>Scheme Execution ID</td><td>Displays the unique identifier of the parent scheme execution. Selecting the ID opens the Scheme Execution Summary pop-up.</td></tr><tr><td>Rule Execution ID</td><td>Displays the unique identifier of the individual rule execution.</td></tr><tr><td>Scheme Rule Name</td><td>Displays the name of the executed rule, helping users identify which validation was performed.</td></tr><tr><td>Function</td><td>Displays the validation logic used for the rule, such as null checks, uniqueness, comparisons, range checks, or pattern validation.</td></tr><tr><td>Connection Name</td><td>Displays the connector or source system where the rule was executed.</td></tr><tr><td>Schema</td><td>Displays the schema name for table-based objects.</td></tr><tr><td>Object</td><td>Displays the associated table, file, or source object where the rule was executed.</td></tr><tr><td>Attribute</td><td>Displays the column or attribute validated when applicable.</td></tr><tr><td>Passed Row Count</td><td>Displays the number of rows that successfully met the rule criteria.</td></tr><tr><td>Failed Row Count</td><td>Displays the number of rows that did not satisfy the rule criteria.</td></tr><tr><td>Total Row Count</td><td>Displays the total number of rows evaluated during execution.</td></tr><tr><td>Result</td><td>Displays the final rule outcome, such as Passed, Failed, Execution Failed, Undetermined, or Not Executed.</td></tr><tr><td>Result Value</td><td>Displays the calculated result value, such as pass percentage, failed percentage, or count, based on the selected function logic.</td></tr><tr><td>Executed By</td><td>Displays the user or system process that triggered the execution.</td></tr><tr><td>Executed On</td><td>Displays the date and time when the rule execution occurred.</td></tr></tbody></table>

**Search, Filter, and Sort**

Users can quickly locate rule execution records using available search and filtering options.

Search helps users find specific rules, objects, or execution identifiers. Filters can be applied for Result, Function, Object Name, Executed By, and execution dates. Sorting can be used for row counts, dates, result values, and execution identifiers.

These capabilities help users quickly isolate failed rule executions, identify heavily impacted objects, and review recent execution activity.

**Result Status Definitions**

* Passed indicates the rule executed successfully, and all evaluated rows met the required criteria.
* Failed indicates the rule executed successfully, but one or more rows did not meet the defined criteria.
* Execution Failed indicates the rule could not complete due to technical issues such as connector errors, query failures, or timeouts.
* Undetermined indicates the rule executed, but a conclusive outcome could not be determined.
* Not Executed indicates the rule was part of the scheme but did not run during the selected execution.

**Failed Values**

Authorized users can review failed values for rule executions that returned failures.

Selecting the failed values option displays sample records or values that did not meet the configured rule criteria. This helps users understand the exact data issue and supports remediation activities.

Failed values are especially useful for:

* Null value violations
* Duplicate records
* Invalid formats
* Out-of-range values
* Pattern mismatches

### Scheme Execution Summary

Selecting the Scheme Execution ID opens the Scheme Execution Summary pop-up.

<figure><img src="/files/ro89GMhzjJUabkzNUI2L" alt=""><figcaption></figcaption></figure>

The Scheme Execution Summary provides a consolidated view of the selected scheme run, allowing users to quickly review execution details without leaving the current page.

Users can review Scheme Name, Status, Object Type, Connector, Object Count, Steward, Run On, Run By, and Run Duration.

The summary also displays Total Rules, Passed Rules, Failed Rules, Failed Rules Percentage, Undetermined Rules, Execution Failed Rules, and Service Requests created during the run.

This helps users understand the overall health and impact of the selected execution while analyzing rule-level results.

#### Export

Users can export the current Scheme Rule Executions view using applied filters and visible records. This helps teams prepare operational reports, share detailed evidence of execution, and perform offline analysis of rule performance.

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ovaledge.com/release8.1/data-quality/data-quality-schemes/scheme-rule-executions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.