Context Window Drift
The Problem
Long conversations lose memory of earlier messages. Chat may forget details, contradict itself, or lose track of your original goal.Solutions
Summarize key findings
Summarize key findings
Periodically ask:Copy the summary, then start a fresh chat with that context.
Start new chats for new topics
Start new chats for new topics
Don’t try to tackle multiple unrelated analyses in one conversation. Split them into separate
chats.
Restate context explicitly
Restate context explicitly
If Chat seems confused, restate your goal:
Query Errors
The Problem
Queries fail to execute or time out.Common Causes
- Too much data: Query spans too many rows or too long a time period
- Complex joins: Multiple table joins slow down execution
- Incorrect table names: Typo or outdated table reference
Solutions
Narrow date ranges
Narrow date ranges
Instead of:Try:
Specify chains/tokens
Specify chains/tokens
Instead of:Try:
Use curated tables
Use curated tables
Flipside’s
ez_* tables are optimized and faster than raw fact tables.Break into steps
Break into steps
For complex analyses, break into sequential queries:
Incorrect or Unexpected Results
The Problem
The numbers don’t match your expectations or known benchmarks.Common Causes
- Token vs USD amounts: Confusing raw token balances with USD values
- Duplicate counting: Rows are joined incorrectly
- Wrong filters: Date ranges, chains, or protocols don’t match your intent
- Data gaps: Some chains or protocols may have incomplete historical data
Solutions
Clarify units
Clarify units
Inspect the SQL
Inspect the SQL
Expand the Flipside Data box and check:
- Filters (WHERE clauses)
- Joins (JOIN conditions)
- Aggregations (SUM, COUNT, AVG)
Sanity-check the numbers
Sanity-check the numbers
Compare to known benchmarks:
- Does this TVL match DeFiLlama?
- Are these volumes consistent with protocol dashboards?
Data Freshness Issues
The Problem
Data seems outdated or doesn’t include the latest activity.Solutions
Check table freshness
Check table freshness
Ask:
Use Live Query Mode
Use Live Query Mode
For truly current data:
text "Use live query to get the latest pool state" Adjust your time range
Adjust your time range
Avoid queries that end “today”—use yesterday or earlier.
Pro Tips for Avoiding Issues
Start simple, then build complexity
Start simple, then build complexity
Begin with a basic query, verify it’s correct, then add layers:
- “Show me Uniswap volumes” (verify this works)
- “Break it down by pool” (add complexity)
- “Add time series” (add more complexity)
Be explicit about everything
Be explicit about everything
- Specify chains: “on Arbitrum” - Specify time periods: “from 2024-01-01 to 2024-03-31” - Specify tokens: “USDC (0xA0b86991…)” - Specify what you want: “in USD, not token units”
Still Stuck?
If you’ve tried these solutions and still can’t resolve the issue:- Simplify your question: Break it into smaller parts
- Start a new chat: Context drift may be causing confusion
- Try a different approach: Ask the same question in a different way
- Contact support: Reach out to Flipside support with details about the issue