ErrorEvent
{
"api_version": 0.1,
"api_event": {
"request_id": [REQUEST_ID],
"error_event": {
"error_code": [ERROR-CODE],
"desc": [DESCRIPTION-OF-ERROR]
}
}
}
There are 7 possible official error_code
s:
InvalidMessageFormat
: If an incoming message is not parsable an ErrorEvent message with this error_code is sent. The desc field will contain more information as to why the message was not parseable. There will be no request_id for all ErrorEvent messages with this code because there is no guarantee the client sent a request_id to begin withMessageNotSupported
: If a client sends a message that is not a valid input message to LabGraph, an ErrorEvent message with this error_code is sent. There will be no request_id for all ErrorEvent messages with this code because there is no guarantee the client sent a request_id to begin withStreamIDNotFound
: If anEndStreamrequest
is sent for a stream that does not exist, anErrorEvent
message with thiserror_code
is sent. *StreamIDAlreadyExists
: If aStartStreamrequest
is sent with astream_id
that already exists in that particular stream, anErrorEvent
message with thiserror_code
is sent. *NotTrained
: If aStartStreamRequest
is sent for a stream that hasn't been trained, anErrorEvent
with thiserror_code
is sent. *StreamAlreadyRequested
: If aStartStreamRequest
is sent for an input stream that has been requested by another session, anErrorEvent
message with thiserror_code
is sent. *NonExistentStream
: If aStartStreamRequest
sent for a stream that is not supported by LabGraph, anErrorEvent
message with thiserror_code
is sent.