Find a query you ran last week.

The problem with "I know I ran this before"

Every SQL editor eventually produces the same moment: you wrote a good query last week, closed the tab, and now need it again but can't remember which connection, which tab, or what you called it. Some tools solve this with a searchable history of every statement ever run. QueryFlow solves a narrower, more deliberate version of it, and it's worth being clear about the difference before you go looking for a feature that isn't there.

What QueryFlow actually keeps

There's no single searchable log of every query you've ever typed. What QueryFlow keeps instead is more selective: in the Ask panel, giving an answer a thumbs up turns it into a verified query, saved on purpose rather than logged automatically. Verified queries are the ones you've already confirmed are correct, kept so you can reuse or reference them instead of re-deriving the same logic from scratch. For scheduled jobs specifically, run history keeps a per-job record of every execution, but that's about whether a job ran, not a general archive of ad hoc queries.

A worked example

Say you asked Claude last Tuesday for last month's churn by region, got a query back, checked it against a number finance already had, and it matched:

SELECT region, COUNT(*) AS churned_customers
FROM ANALYTICS.PUBLIC.CUSTOMERS
WHERE churn_date >= DATE_TRUNC('MONTH', CURRENT_DATE) - INTERVAL '1 MONTH'
AND churn_date < DATE_TRUNC('MONTH', CURRENT_DATE)
GROUP BY region;

If you gave that answer a thumbs up when you first saw it, it's sitting in verified queries now, findable and reusable the next time someone asks for the same cut. If you didn't, it's back to reconstructing it from memory, the same as it would be in a tool with no history feature at all.

Practical habits that cover the gap

• Thumbs up an Ask answer the moment you've verified it's correct, not later when you might forget which one it was.
• Keep frequently reused queries in a Flow Book with a clear name, rather than trusting you'll remember which open tab had it.
• For anything that runs on a schedule, job run history already gives you the record automatically; you don't need to do anything extra there.

What this isn't

This isn't a full-text search across every statement you've ever executed, and it isn't trying to be. A general history log tends to accumulate noise, half-finished drafts, typo'd queries, exploratory dead ends, until finding the one good query in it is its own search problem. Verified queries are smaller and more deliberate by design: what's in there is there because you decided it was worth keeping, not because the app logged it automatically.

If you need a broader audit trail

For a compliance or audit use case where every statement run against a database needs to be logged regardless of whether anyone marked it useful, that's a job for the warehouse's own query history, Snowflake's QUERY_HISTORY view or BigQuery's job history, not a client-side feature. QueryFlow is where you write and verify queries; the warehouse itself is the more complete and more durable record of everything that actually executed against it.

Naming things so future-you can find them

Since there's no automatic log to fall back on, naming discipline does more work here than it would in a tool with full history search. A Flow Book called Untitled 3 is unfindable in three weeks; one called Monthly Churn by Region is findable by scanning a short list of tabs. The habit that actually solves "I know I wrote this somewhere" isn't a search feature, it's naming things clearly the moment you write them, before you've forgotten what made that version different from the other five attempts.

A second scenario: the query you forgot to verify

Say you asked a question on a Friday afternoon, got an answer, glanced at it, and moved on without a thumbs up either way. The following Monday, you need the same cut and can't find it in verified queries, because it was never marked as one. This isn't a bug, it's the tradeoff of a deliberate rather than automatic history: the fastest fix in the moment is asking the same question again rather than hunting for an unverified answer that was never saved anywhere findable. Going forward, making the thumbs up a reflex the moment you trust an answer is the cheaper habit than trying to reconstruct one you skipped.