Skip to content

Edit a Freshness Check

Step-by-step tutorial for changing the Maximum Age of an existing Freshness check. For which values can and cannot change, see the API page's editable and immutable lists.

Permission Required

You need the Author team permission on the datastore to edit an Active check, or Drafter to edit a Draft. See the Permissions page for the full matrix.

Only changing the Maximum Age?

The Observability chart has an inline editor for the Maximum Age alone. See Edit Maximum Age.

What Happens to Existing Anomalies

Saving the edit changes only the check. The anomalies it already produced are not deleted, modified, or re-evaluated at save time.

The updated rule takes effect on the next Scan of the container: run one manually or wait for the scheduled operation. Until that scan runs, the anomaly list stays exactly as it was. On that scan:

  • A new anomaly can appear. If the check still fails, a new Shape Anomaly is reported. When Archive Duplicate Anomalies is on, a finding that matches an anomaly that is still open (same check, same fingerprint) is archived as Duplicate instead of opening a new one.
  • Old anomalies stay open. Anomalies raised under the previous configuration keep their status until you triage them, or until a Full scan with Auto Resolve resolves what the updated rule no longer flags.

Editing an AI Managed check

Changing the Maximum Age of an AI Managed Freshness check converts it to Authored. Qualytics then stops updating it from new measurements. See AI Managed Freshness Checks.

Steps

Step 1: Select the source datastore from the left menu, then click the Checks tab.

Step 2: Locate the check you want to edit and click it, or open its Settings menu and select Edit . The check details form opens: Authored Check Details, or AI Managed Check Details for an AI Managed check.

Step 3: To change the Maximum Age, click Edit value next to it. The Unit and Maximum Age inputs open with the current value.

Step 4: Change the values you need in each section of the form. Each field is described in the create how-to's Field reference.

  • Target: nothing to change here. The container is locked after creation, and the rule has no field, filter, or custom anomaly description.
  • Properties: the Unit and the Maximum Age.
  • Ownership: the Owner and the Anomaly Assignee.
  • Metadata: the Description, Tags, and Additional Metadata.

Locked after creation

The table or file the check runs against and the Rule Type are locked once the check is saved. To change either, delete the check and create a new one.

Step 5: Click Validate to test the updated configuration without saving it. A success message confirms the rule can run. If validation fails, see Troubleshooting. The Validate button needs the Author team permission, so it does not appear for a Drafter, who can skip this step.

Step 6: Click Update. A success message confirms that the check was updated.