Dry Run a Check¶

Run a check against a sample of its data to see what it would flag, without creating anomalies or running a Scan. Use it to test a new or edited check before it goes live. For what the results show, see Dry Run.

Permission Required

Running a Dry Run requires the Drafter, Author, or Editor team permission on the check's datastore. Revealing masked values in the results requires Editor. See Team Permissions.

Steps¶

Step 1: Open the Checks tab of the datastore, table or file, or field that holds the check.

Step 2: Click the Active or Draft tab, depending on the check's status. To narrow the list, pick a subtab, such as Important, Owned, or Favorite, or search and filter it. See Filter and Sort Checks.

Step 3: Click the check. Its page opens.

Step 4: Click at the top right. A menu opens.

Step 5: Click Dry Run . The Dry Run Results dialog opens and shows its progress while it prepares the data, asserts the check, and scans for anomalous data.

Step 6: Review the results: the anomalies found, with their asserted and anomalous record counts, and the source records behind them. When nothing fails, the dialog reads No anomalies were identified.

Step 7: Optionally, click Download source records to save the evaluated records as a CSV file.

Draft checks too

A Draft check can be dry run as well, so you can test its logic before you activate it.