Skip to content

Data Suitability Recipe Troubleshooting

This page documents the known problems while running the Data Suitability recipe and working with the AI Use Cases it creates, and the steps to resolve them. Each section describes a symptom, its cause, and the resolution.

Defining the Use Case

The Record List Is Empty or a Record Is Missing

The list under Data Suitability shows "No model risk records yet." although records exist, or a record you know of is not listed.

Cause: The list only shows use cases whose every bound datastore you can see with the Viewer team permission or above. A record that binds even one datastore you cannot reach is hidden entirely, and its page is not found.

Resolution: Ask for Viewer on the missing datastore, or ask the record's owner which datastores it binds. See Permissions.

Creating the Record Is Refused

Clicking Next on the Model step fails with a permission error.

Cause: Creating a use case needs the Author team permission on at least one datastore, and binding datastores later needs Author on each of them. A user with only Viewer access cannot create records.

Resolution: Request the Author team permission on the datastores the model reads, then try again.

The Name Is Already Taken

Saving the Model step fails with a message that a use case with that name already exists.

Cause: AI Use Case names are unique. Another record, possibly one you cannot see, already carries the name.

Resolution: Add the version or the team to the name, for example "Retail Credit Scoring v4 (Risk)".

No Containers Appear on the Inputs Step

After selecting a datastore, the step shows "No containers found. The selected datastores have no containers yet. Run a profile operation first."

Cause: The datastore's containers have not been discovered yet, or the profile that populates their metadata has never run.

Resolution: Run a Sync and a Profile operation on the datastore, then reopen the step.

A Binding Is Rejected as Out of Scope

Saving Inputs or Standard fails with a message that containers or checks are outside the bound scope.

Cause: Containers must belong to a bound datastore, and checks must belong to a bound container or datastore. Removing a datastore while its containers or checks are still bound produces this error.

Resolution: Bind the datastore first, or clear the containers and checks that belong to the datastore you removed.

Capturing the Evidence

Capture Baseline Is Refused

Clicking Capture Baseline fails with "Cannot capture a baseline: no containers are bound to this AI use case".

Cause: The baseline snapshots the bound containers, so it needs at least one.

Resolution: Go back to Inputs, bind the containers the model reads, and capture again.

Generate Attestation Stays Disabled

On the Evidence step, Generate Attestation cannot be clicked.

Cause: Generation needs both a captured baseline and a Certified record. The step warns when the baseline is missing and shows the certification badge and the transitions available to you.

Resolution: Capture the baseline on the previous step, then get the record certified. See Certify an AI Use Case.

Nobody Can Click Certify

The record is In Review, but the Evidence step and the AI Use Case page offer no Certify button to anyone on the team.

Cause: Certifying needs the Manager role together with the Editor team permission on every bound datastore, or the Admin role. A Manager who holds only Author or Viewer on one of the datastores cannot certify, and neither can the record's author, whatever their permissions.

Resolution: Find a Manager with Editor on all the bound datastores, or an Admin, and share the page with them. Qualytics does not send an approval notification.

Generation Fails Because the Scope Changed

Clicking Generate Attestation fails with "Cannot generate an attestation because the asset scope changed after baseline capture".

Cause: Containers were bound or unbound after the baseline was captured. A baseline describes one scope, and drift against it is meaningless for containers it never snapshotted.

Resolution: On the Baseline step, click Start New Baseline. This returns the record to Draft, so submit it for review and have it certified again, then generate the attestation. See Start a New Baseline.

The Attestation Disappeared from the Run

After editing the record, the Evidence step no longer shows the attestation the run produced and asks for a new one.

Cause: The recipe ties the run's attestation to the definition it was generated from. When the name, tier, bindings, checks, schedule, or certification change, the existing attestation no longer describes the record, so the run treats it as outdated. The attestation itself is untouched and still listed under History on the Attestations tab.

Resolution: Generate a new attestation once the record is certified again. Use the history to retrieve the earlier one when you need it.

Records and Certification

The Record Reads Expired Although Nothing Ran

A certified record shows Expired without any scheduled check having run.

Cause: Expiry is derived from the certification's validity date. Once the date passes, the record reads as Expired everywhere, even before the scheduled check updates the stored state.

Resolution: Submit the record for review again and have it certified anew, with a new validity date if needed.

The Scheduled Expiry Check Did Nothing Else

The expiry schedule ran, but no scan, profile, baseline, or attestation happened.

Cause: That is by design. The schedule only updates a Certified record to Expired after its validity date. It never touches source data or generates evidence.

Resolution: Schedule Profile and Scan operations on the datastores themselves, and generate new evidence after the next governance review.

Progress Is Not Being Saved

The side panel footer reports a failed save while you work through the recipe.

Cause: Saving progress needs the Author team permission on every bound datastore, and Members can only save on records they created. Viewing the record is enough to browse it in the recipe, but not to save.

Resolution: Ask for the missing team permission, or ask the record's owner or a Manager to continue the run. Your changes to the definition itself are refused for the same reason.

The Recipes Card Never Shows Continue

The Data Suitability card on the Recipes page always reads Get Started, even with a run in progress.

Cause: This recipe saves progress on the AI Use Case, not in your browser, so the card cannot know which record you were working on.

Resolution: Resume from the record list with Open in Recipe, or from the AI Use Case page with Continue Recipe. See Resume a Recipe from an AI Use Case.

No Attestation Was Current on the Selected Date

Under Attestation as of a date, Retrieve reports that no attestation was current on that date.

Cause: The lookup returns the newest attestation generated on or before the date. Before the first attestation existed, there is nothing to return.

Resolution: Pick a date on or after the first generation shown under History.

Limitations

  • The recipe records evidence about structured inputs only. It does not assess whether a model's or an agent's output is correct.
  • Certification and evidence generation are two separate jobs by design; there is no single-user path from Draft to attestation.
  • Qualytics does not notify approvers. Share the AI Use Case page when you submit for review.
  • Exports are JSON and HTML only.