Interface: ConversationStreamErrorEvent
@kortexya/reasoninglayer / ConversationStreamErrorEvent
Interface: ConversationStreamErrorEvent
Section titled “Interface: ConversationStreamErrorEvent”Defined in: src/types/conversation.ts:862
The pipeline failed after the stream opened. The stream ends after it.
Remarks
Section titled “Remarks”status is the HTTP status the blocking sendMessage would have raised for
the same failure (for example 502 when the LLM is unreachable). The
blocking route’s error body is { error: text, message: text }, and this
event carries the same text, so
createApiError(event.status, { error: event.error, message: event.error }, new Headers())
gives the same error subclass, message and errorCode that sendMessage
throws for the failure.
An event without status is not an HTTP failure: the engine could not
serialize its terminal event. Treat it as a plain error.
The stream yields this event and does not throw it, so a caller can tell a failure after the stream opened (the turn ran) from a refusal before it opened (thrown on the first pull; the turn did not run).
Properties
Section titled “Properties”error:
string
Defined in: src/types/conversation.ts:868
The engine’s error text.
status?
Section titled “status?”
optionalstatus?:number
Defined in: src/types/conversation.ts:866
HTTP status of the failure, when the engine reported one.
type:
"error"
Defined in: src/types/conversation.ts:864
Discriminator.