Check an answer
Check the interpretation, SQL and context behind an answer before relying on a number.
What to check
- Interpretation
- The business meaning, period, grain and filters Cassis applied. A definition question can be answered without SQL.
- SQL and results
- The generated SQL and its results. On a schema-only project, SQL is not executed and
resultsisnull. Zero rows means a query ran and matched nothing. - Objects used
- The tables, joins and metrics the answer used. An unexpected one is a reason to look closer.
- Context version
- A conversation keeps the context version it started on. To check a published fix, start a new conversation.
When an answer looks wrong
- Wrong number
- Check the interpretation and SQL. If the rule is wrong, correct it in the conversation and rate the answer down with the rule you expected. If you are unsure of the rule, ask its owner.
- No result
- Check whether the SQL ran, returned zero rows, or failed. When the data cannot answer, Cassis says what is missing: “What is our refund rate?” fails when nothing in the data records a refund.
- Old definition
- The conversation may predate a fix. Ask again in a new conversation, and check which version is live.
- Error
- The message tells credentials, permissions, connection failures and timeouts apart. See Limits and errors.
A correction or a rating does not change the shared context by itself. It becomes evidence your data team sees in Review once Cassis analyzes the chat with Cassis. When you use a connected assistant, ask it to send the correction or feedback to Cassis.