Curate an app-managed project

You need edit access to an app-managed project and an issue you decided to fix in triage. With no issue behind the change, edit the context in Explorer or ask the context Assistant, then continue at step 3 from Unpublished changes. On a git-managed project, follow Curate a git-managed project instead. If domains, tables, and metrics are new to you, first explore a real context.

1. Open the issue

In Review, open the issue to fix. In this example, someone asked “How many active customers do we have?” and nothing in the context defines an active customer. The issue’s evidence shows the question and the rule the asker gave in their chat: at least one delivered order in the last 90 days. Read every occurrence before deciding the fix.

If people have asked questions since the last analysis, choose Analyze conversations to look for new issues.

Unreliable answer Context gap

"Active customer" has no agreed definition

A question about active customers stopped because nothing in the context defines the term. The asker supplied a rule in the conversation, so the answer holds for that chat only.

Occurrences (1)

Chat chat_message

"How many active customers do we have?" → Cassis asked what makes a customer active. Reply: at least one delivered order in the last 90 days.

Proposed fix

Add metric active_customers ready

Count distinct customers, by CUSTOMER_UNIQUE_ID, with at least one delivered order in the last 90 days.

✓ Apply fix Fix in chat ✕ Dismiss

2. Decide the rule

A reply in one chat is evidence, not an agreed definition. Check the proposed rule with the person who owns customer reporting before you apply it. For this historical example, use delivered orders placed in the 90 days ending at the dataset’s latest order purchase timestamp. If they want a different window or a different count, use Fix in chat instead of Apply fix: it opens the context Assistant on the issue, where you give it the agreed rule. On main, the published line, the Assistant proposes its changes for you to approve.

3. Apply and review the diff

Choose Apply fix, then open Unpublished changes. Check that the diff adds one active_customers metric with the agreed rule and changes nothing else.

Metrics+1 added

→ active_customers added

+ name: active_customers + description: Customers with at least one delivered order placed in the last 90 + days of this dataset. Use the latest order purchase timestamp as the reference + date. Count people by CUSTOMER_UNIQUE_ID; CUSTOMER_ID changes with every order. + expression: COUNT(DISTINCT "CUSTOMER_UNIQUE_ID") + filters: STALLORA.ORDERS.ORDER_STATUS = 'delivered' + AND STALLORA.ORDERS.ORDER_PURCHASE_TIMESTAMP >= DATEADD(day, -90, + (SELECT MAX(ORDER_PURCHASE_TIMESTAMP) FROM STALLORA.ORDERS)) + (requires JOIN CUSTOMERS.CUSTOMER_ID = ORDERS.CUSTOMER_ID) + synonyms: [active customer count, currently active customers]

Label: Define active customers

On main, only eval cases can test the change before publishing, because a chat on main uses the published context. To ask the question against the fix first, which matters when no case covers it yet, make the change on a Cassis branch and ask in a chat there.

4. Test, publish and verify

In Unpublished changes, choose Publish (on a Cassis branch, Merge into main). Nothing runs the eval cases on its own: in the Publish dialog, choose Run evals to score them against exactly the changes you are publishing (a matching run you already made is reused). Publish with a clear version label once they pass. Publishing runs in the background; closing the tab does not cancel it.
In a new conversation, ask “How many customers are currently active?” It should answer without asking, list active_customers among the objects used, and count customers with a delivered order in the last 90 days.
If the issue is still open, resolve it in Review: the published version now carries the fix.
Once the owner validates that answer’s SQL, choose Add as test case so a later change cannot break it. If the change makes answers worse, roll it back.

Git-managed project? Read the issue here, but make the change in the repository, so a later import from Git does not overwrite it: Curate a git-managed project.