Asking ChatLimits & best practices
Asking ChatLimits & best practices
Limits & Best Practices
Current limits
| Limit | Value |
|---|---|
| Max rows Chat can query per request | 5,000,000 |
| Max conversation history retained | 100 messages |
| Max concurrent Chat sessions per workspace | 10 |
| Chat response timeout | 30 seconds |
| Max widgets Chat can create per message | 3 |
Best practices
- Name your data sources and dashboards clearly. Chat uses these names to resolve your intent.
- If Chat misidentifies a data source, specify it explicitly: "from my PostgreSQL connection named 'prod-db'".
- For complex multi-step analysis, break it into separate messages rather than one long prompt.
- Chat does not retain context between sessions. Start a new session with a brief summary if continuing previous work.
- Avoid asking Chat to write to your data — it's read-only by design.