[Read on Dashport](https://dashport.ai/documentation/limits-and-best-practices)

Asking ChatLimits & best practices

Copy page

[

Dashport Docsv2.0](/documentation)

Getting Started

IntroductionCreating your account5-minute quick start

Connecting Data

Supported integrationsConnect a databaseColumn comments & AI contextSuperSheets as a sourceCredential securityRefresh intervals

Using SuperSheets

What is SuperSheets?Creating a sheetData entry & column typesFormulas & calculationsFormatting & selectionSort, filter & columnsRow operationsValidation & frozen panesImport & exportSharing & activity logKeyboard shortcutsUse as a data source

Asking Chat

How Chat worksWriting effective promptsExample conversationsBuilding charts via ChatLimits & best practices

Building Dashboards

Three ways to buildDrag-and-drop builderAsk Chat to buildSharing & permissions

Asking ChatLimits & best practices

Copy page

## Limits & Best Practices[](#ch-limits)

### Current limits[](#ch-limits-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[](#ch-limits-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.

Previous

Building charts via Chat

Next

Building Dashboards
