Debug Query Suggestions

​

Prerequisites

• A source where Debug is available — a data warehouse or query engine source that Validio validates through SQL pushdown. See Debugging an Incident.
• The Allow LLM credentials setting enabled in your Validio Workspace. See Managing Workspace Settings.
• At least one LLM credential configured in your environment. Validio runs no model of its own, so the Suggest query button stays disabled until you configure one. See LLM Credentials.
• Permissions in the namespace as follows. See Managing Roles.

​

Ask for a suggestion

1. Open Debug on an incident, from an incident group details page or anywhere individual incidents are listed.
2. Select Suggest query in the toolbar above the editor. A prompt slides in beneath the toolbar.
3. Describe what you want the query to show — for example, break the drop down by region and channel or compare this window against the same day last week.
4. (Optional) Choose which LLM credential to ask with, from the menu on the send button. Validio uses the first configured credential by default.
5. Send the ask. Suggest query becomes a progress indicator while the agent works; hover or select it to see the per-step detail:

   Step	What happens
   Gathering incident context	Validio gathers context about the incident
   Designing the debug query	The model writes the query and Validio runs its own checks on it

​

Read the suggestion

-- Wholesale channel volume by region
-- ROW_COUNT fell 38% below the lower bound. Broken down by region and
-- channel to find where the rows went; built on the saved query "Daily
-- volume by region".
SELECT
  region,
  channel,
  COUNT(*) AS row_count
FROM "analytics"."orders"
WHERE CAST("created_at" AS TIMESTAMPTZ) >= {{ validio_incident_window_start() }}
  AND CAST("created_at" AS TIMESTAMPTZ) < {{ validio_incident_window_end() }}
GROUP BY region, channel
ORDER BY row_count ASC
LIMIT 50

​

Remaining checks

-- Check: validio_incident_window_start: was in the generated base query and
-- is gone, so the suggestion no longer re-binds to a later incident.

​

Edit, run, save, or discard

• Run it to load sample records, as with the generated query.
• Edit the SQL freely. Reset returns the draft to the SQL the agent wrote.
• Save it to keep it against the validator for future incidents, under a name of your choosing. See Saving and reusing a debug query.
• Discard it if it is not useful. Nothing was stored, so there is no confirmation step.

​

Iterate on a query

• The SQL currently in the editor, including any edits you made.
• Whether that SQL is still the agent’s own last suggestion, unchanged.
• Your warehouse’s error message, if the last run of that query failed.

​

What the agent reads

• Incident details — the validator’s configuration, the window that fired, and how far the value deviated from its threshold.
• Catalog metadata — names, data types, and descriptions for the source’s columns. See Catalog Assets.
• Related incidents and lineage — what else is firing nearby, and whether the cause looks upstream. See Root Cause Analysis.
• Previously saved queries — the validator’s saved debug queries, as worked examples of how your team investigates this check.
• Your ask — what you typed, passed to the model verbatim.

​

Cancel a run

​

Related resources

• Debugging an Incident
• Debug Query Syntax
• Root Cause Analysis
• LLM Credentials
• AI Data Transparency
• About Validio AI Features