Query history and saved queries
Review every query run in a workspace in Run History - timing, status, user, and query text - and get query counts programmatically.
Every query run in the workspace is recorded in Run History, accessible from the left navigation of the Compute Plane. Use it for debugging slow queries, auditing access, cost attribution, and finding patterns.
What's recorded
Query ID
Unique identifier (copy this when contacting support)
User
Who ran the query
Cluster
Which cluster executed it
Catalog
Primary catalog used
Status
Success, Failed, Timed out, Cancelled
Submitted at
When the query arrived
Started at
When execution began (may differ if the cluster was scaling)
Duration
End-to-end time
Bytes scanned
Data read from storage
Rows returned
Result set size
Cache
Hit, Miss, or Bypass
Execution mode
Standard or Native
Access method
UI, JDBC, REST, PG protocol, and so on
Query text
The SQL submitted (and the translated SQL if the transpiler is enabled)
Filtering and searching
Run History supports filters by time (last hour, day, week, or custom range), user, cluster, status, and access method, plus full-text search within query text. Combine them for targeted investigation - for example, "all failed JDBC queries from bi-service-account in the last 24 hours."
Click a query to drill into its full text, execution plan (if available), per-stage resource usage, error details, and the cluster state at execution time. Copy the Query ID to share with e6data support.
Common workflows
Debug a slow query: filter by status
Success, sort by duration descending, open the slowest queries, and look for full table scans, missing partition pruning, or large joins without predicates.
Exporting and retention
Export filtered query history to CSV or to your data warehouse via the REST API.
See also
Last updated
Was this helpful?