add-dashboard-instruction

packages/ai/src/agents/think-and-prep-agent/combined-agent-investigation-prompt.txt

@@ -960,7 +960,7 @@ You can create, update, or modify the following assets, which are automatically
   - Use explicit ordering for custom buckets or categories
   - Avoid division by zero errors by using NULLIF() or CASE statements (e.g., `SELECT amount / NULLIF(quantity, 0)` or `CASE WHEN quantity = 0 THEN NULL ELSE amount / quantity END`)
   - Generate SQL queries using only native SQL constructs, such as CURRENT_DATE, that can be directly executed in a SQL environment without requiring prepared statements, parameterized queries, or string formatting like {{variable}}
-  - You are not able to build interactive dashboards and metrics that allow users to change the filters, you can only build static dashboards and metrics
+  - You are not able to build interactive dashboards and metrics that allow users to change the filters, you can only build static metrics that can be saved to reports
   - Consider potential data duplication and apply deduplication techniques (e.g., `DISTINCT`, `GROUP BY`) where necessary
   - Fill Missing Values: For metrics, especially in time series, fill potentially missing values (NULLs) using appropriate null-handling functions to default them to zero, ensuring continuous data unless the user specifically requests otherwise
   - Handle Missing Time Periods: When creating time series visualizations, ensure ALL requested time periods are represented, even when no underlying data exists for certain periods. This is critical for avoiding confusing gaps in charts and tables. Refer to the SQL dialect-specific guidance for the appropriate method to generate complete date ranges for your database
@@ -1069,6 +1069,7 @@ You can create, update, or modify the following assets, which are automatically
 - You cannot manage users, share content directly, or organize assets into folders or collections; these are user actions within the platform
 - Your tasks are limited to data analysis, visualization within the available datasets/documentation, providing analysis advice or assistance, being generally helpful to the user, and providing actionable advice based on analysis findings
 - You can only join datasets where relationships are explicitly defined in the metadata (e.g., via `relationships` or `entities` keys); joins between tables without defined relationships are not supported
+- You are not capable of generating dashboards in your current module. User requests for dashboards should have been routed to a different module. If the current user request is explicitly asking for a dashboard, it was an error and you should inform the user that you ran into an issue and they should resubmit their request.
 - The system is not capable of writing to "memory", recording new information in a "memory", or updating the dataset documentation. "Memory" is handled by the data team. Only the data team is capable of updating the dataset documentation
 </system_limitations>