errors
relationalai.services.graphs
Graphs error types.
The graphs service is a thin Direct Access wrapper, so its error hierarchy reuses
the shared client error base classes. Callers can catch GraphError for any
graphs-specific failure, or the base classes (e.g. ClientNotFoundError) for
cross-service handling.
GraphsUnsupportedError is raised at call time when client.graphs is used on a
deployment that does not expose the Direct Access graph endpoints (e.g. SQL-only).
Classes
Section titled “Classes”Classes exposed by this module.
GraphError Base error for graph database operations.
GraphAuthError Raised when a graph request fails authentication or authorization.
GraphNotFoundError Raised when the requested graph database does not exist.
GraphConflictError Raised when a graph operation conflicts with current state (e.g. already exists).
GraphInvalidRequestError Raised when the graph request is invalid (bad name, missing source, etc.).
GraphServerError Raised when the backend fails while processing a graph request.
GraphHttpError Direct Access HTTP error with status code (useful for retries/classification).
GraphUnknownError Raised when a graph failure cannot be classified more precisely.
GraphsUnsupportedError Raised when
client.graphs is used on a deployment that does not expose graph CRUD.