# Scheme Executions

The Scheme Executions page helps users review the historical execution activity of a Data Quality Scheme. It enables stewards and administrators to monitor scheme performance, identify recurring failures, investigate technical issues, and analyze quality trends across previous runs.

Each record represents one completed or attempted scheme execution. Users can search, filter, and sort execution history; export execution history; review logs; and open execution summaries for detailed analysis.

This page is commonly used to assess whether schemes are running successfully, how rule outcomes change over time, and where remediation attention is required.

<figure><img src="/files/1z8cECLclwTduHcBquBB" alt=""><figcaption></figcaption></figure>

### Execution List View

The Execution List View displays all historical runs of the selected Data Quality Scheme. Each row represents a single scheme execution and provides key operational, performance, and results details to help users monitor scheme activity.

<table><thead><tr><th width="199.33331298828125">Field</th><th>Description</th></tr></thead><tbody><tr><td>Logs</td><td>Displays the log icon. Selecting the icon opens the Logs pop-up for the selected execution, where users can review runtime messages, warnings, and errors.</td></tr><tr><td>Scheme Execution ID</td><td>Displays the unique identifier of the scheme execution. Selecting the ID opens the Execution Summary pop-up with complete run details.</td></tr><tr><td>Result</td><td>Displays the final execution outcome, such as Passed, Failed, Execution Failed, Undetermined, or Not Executed. This helps users quickly understand the run status.</td></tr><tr><td>Passed Rules</td><td>Displays the number of rules that completed successfully and met their success criteria during the execution.</td></tr><tr><td>Failed Rules</td><td>Displays the number of rules that executed successfully but failed validation checks.</td></tr><tr><td>Execution Failed Rules</td><td>Displays the number of rules that could not be completed due to technical issues such as connector failures, query errors, or timeouts.</td></tr><tr><td>Undetermined Rules</td><td>Displays the number of rules where a conclusive pass or fail result could not be determined.</td></tr><tr><td>Total Rules</td><td>Displays the total number of rules included in the selected scheme execution.</td></tr><tr><td>Start Time</td><td>Displays the date and time when the scheme execution started.</td></tr><tr><td>End Time</td><td>Displays the date and time when the scheme execution completed.</td></tr><tr><td>Duration</td><td>Displays the total execution time calculated between Start Time and End Time. This helps users identify long-running executions.</td></tr><tr><td>Run By</td><td>Displays the user or system process that initiated the scheme execution.</td></tr></tbody></table>

**Search, Filter, and Sort**

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

Search helps locate specific executions using execution identifiers or related details. Filters can be applied for Result, Run By, and execution date ranges. Sorting can be used on numeric, date, and timestamp fields such as Start Time, End Time, Duration, and rule counts.

These options help users isolate failed runs, recent executions, long-running jobs, or executions triggered by specific users.

**Result Status Definitions**

* Passed indicates all active rules completed successfully and met their criteria.
* Failed indicates one or more rules completed execution but failed validation.
* Execution Failed indicates the scheme or one or more rules encountered technical issues such as connector problems, query failures, or system interruptions.
* Undetermined indicates rules executed, but no conclusive result could be produced, such as insufficient qualifying data.
* Not Executed indicates the scheme was created or scheduled, but no actual validation occurred.

These statuses help users quickly understand scheme health and operational reliability.

### Logs

Selecting the **Logs** eye icon opens the Logs pop-up for the selected Scheme Execution.

<div align="left"><figure><img src="/files/QVUdVPOH6Gy0m4OiQ4Bb" alt="" width="375"><figcaption></figcaption></figure></div>

The Logs pop-up displays detailed runtime messages generated during execution. It helps users investigate failures, monitor progress, and review execution activity without leaving the current page.

Users can search log messages, filter entries by Info, Warning, or Error levels, and use the calendar to review logs for a specific date or time period.

Refresh reloads the latest log entries. Download exports the log details for offline troubleshooting, incident review, or support analysis.

Logs are especially useful when the execution result is Execution Failed or when runtime delays need to be investigated.

### Execution Summary

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

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

The Execution Summary provides a consolidated view of the selected run, enabling users to quickly understand the outcome, performance, and operational impact without navigating away from the execution list.

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

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

This helps users assess scheme health, understand the severity of failures, and prioritize remediation actions.

### Export

Users can export the current Scheme Executions view using the applied filters and visible records. This helps teams prepare operational reports, review historical execution trends offline, or share run activity with governance and support teams.

***

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-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.