Errors and retries

Status: The source SDK’s minimal durable methods work with the live partner-preview gateway. The package is not published to npm. Turn streaming remains unavailable; exact approval remains pending activation. Cancellation-reconciliation code is deployed, but final-status behavior remains pending a separate live canary.

​

Two failure lanes

1. A rejected HTTP request can throw AiPlatformHttpError. Its validated .problem can still be null when a proxy/body is not valid application/problem+json.
2. An accepted durable task reports execution failure through a terminal run.failed event and RunResource.failure. It does not emit the turn-only request.failed event.

import { AiPlatformHttpError } from "@nexislabs/ai-platform";

try {
  const run = await client.execute(request);
  for await (const event of client.streamRunEvents(run.run_id)) {
    if (event.type === "run.failed") handleRunFailure(event.failure);
  }
} catch (error) {
  if (error instanceof AiPlatformHttpError) {
    handleHttpProblem(error.status, error.problem);
  } else {
    throw error;
  }
}

​

HTTP retry rules

• problem.retryable is authoritative when a valid problem exists.
• Honor Retry-After or retryAfterMs when supplied.
• Authentication, authorization, entitlement, validation, and conflict errors require a credential, authority, request, or state change.
• Schema/stream parser errors are client/contract bugs, not transient network errors.
• Abort errors stop the local request/read; they do not prove a durable task stopped.

​

Idempotency

​

Durable SSE reconnect

​

Cancellation

The run is reconciling an uncertain execution outcome. Do not retry or resubmit it.

{
  "code": "run_outcome_unknown",
  "message": "A committing action may have happened, but the final outcome could not be verified. Do not retry automatically.",
  "retryable": false
}

​

Offline turn schemas