Skip to main content
POST
Retry a failed turn (async)

Authorizations

Authorization
string
header
required

Use Authorization: Bearer <token>. The token is either a user token / OAuth access token, or a service-account API key (cfk_...). A key is valid on every endpoint and acts as its service account, an organization member with per-store permissions. Refused keys answer 403 with Invalid API key., API key revoked., API key expired. or API key disabled..

Headers

X-Impersonate-Email
string<email>

Email of the user to impersonate. Requires CAN_IMPERSONATE_OTHER_USERS permission. If the target user is not found or does not have access to the project, the request proceeds as the authenticated user. Contact Clarifeye to enable this permission.

Path Parameters

project_id
string<uuid>
required

UUID of the project

conversation_id
string<uuid>
required

UUID of the conversation

Response

Retry accepted and enqueued; poll for progress

In-flight turn state returned by the async send_message (202) and poll endpoints for playground and Work-with-Clara conversations.

id
string<uuid>
turn_status
enum<string>

Lifecycle of the current chat turn

Available options:
idle,
running,
failed
turn_error
string

User-facing reason when turn_status is failed (empty otherwise). Never the raw exception: the error_ref in the streaming_error payload finds it.

turn_events
object[]

Accumulated message-level events for the current turn. Each item mirrors a former SSE frame: {type_streaming, payload} where type_streaming is one of streaming_in_progress, streaming_error, streaming_completed, or quick_replies_ready (Clara only). A streaming_error payload carries category (provider_unavailable, provider_declined, unexpected), error_ref and content; the turn is then closed in chat_history by a turn_error entry, answerable with retry-turn.

updated_at
string<date-time>

Last activity timestamp; doubles as the turn staleness heartbeat