Error codes - e6data Docs

When something goes wrong, e6data returns a structured error with a code, message, and (often) details. This section is the reference for what each code means and how to resolve it.

Error categories

Category	When you’ll see it
Catalog errors	Catalog creation, refresh, or connection issues
Cluster errors	Cluster lifecycle and execution issues
Connectivity errors	Network, endpoint, and reachability issues
Data governance errors	Permission and policy enforcement
General errors	Platform-level errors not specific to a component
Query editor errors	SQL Editor-specific issues
Query history errors	Run History retrieval and filtering
REST API errors	REST API-specific errors
User account errors	Authentication, profile, and account
Workspace errors	Workspace lifecycle and management

Reading an error

Errors include three things:

Code - a short, stable identifier (e.g., CLUSTER_SUSPENDED)
Message - a human-readable summary
Details - context-specific data when relevant

When opening a support ticket, include the code, message, and any IDs from the details.

Common patterns

Pattern	Likely cause
`*_NOT_FOUND`	Resource doesn’t exist, or your token doesn’t have permission to see it
`*_TIMEOUT`	Configured timeout exceeded; tune or retry
`RATE_LIMITED`	Too many requests; back off
`*_PROVISIONING`	Resource being created; wait
`*_SUSPENDED`	Resource is paused; resume or wait for auto-resume

See also

SQL reference
Limitations - known limits that might surface as errors

Last modified on October 1, 2026