Skip to content

Exceptions

The high-level client raises SDK exceptions for HTTP error responses rather than returning error models as operation results:

  • HTTP 422 raises OblidogValidationError.
  • Typed integration run conflicts raise OblidogConflictError; its code contains the integration conflict reason.
  • Other HTTP errors raise OblidogApiError.

These exceptions preserve the original HTTP status in status_code and the complete response bytes in content, including error codes and params. Undocumented statuses also raise OblidogApiError with the generated exception retained as the cause.

OblidogError

Bases: Exception

Base exception raised by the high-level Oblidog client.

OblidogApiError

Bases: OblidogError

The Oblidog API returned an unexpected response.

OblidogValidationError

Bases: OblidogError

The API rejected request parameters or payload with HTTP 422.

status_code and content preserve the original HTTP error response.

OblidogConflictError

Bases: OblidogApiError

A registry operation conflicted with the current state or revision.

code retains the typed integration conflict reason. content keeps the complete response body, including top-level error metadata and params.

OblidogConnectionError

Bases: OblidogError

The Oblidog API is temporarily unreachable.

Raised when an HTTP transport failure cannot be recovered, or when a retryable HTTP 502, 503, or 504 response persists after all configured attempts. The original httpx.TransportError is preserved as the exception cause when the failure originates in the HTTP transport.