WebSockets API Error Codes¶
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 anEndStreamrequestis sent for a stream that does not exist, anErrorEventmessage with thiserror_codeis sent. *StreamIDAlreadyExists: If aStartStreamrequestis sent with astream_idthat already exists in that particular stream, anErrorEventmessage with thiserror_codeis sent. *NotTrained: If aStartStreamRequestis sent for a stream that hasn’t been trained, anErrorEventwith thiserror_codeis sent. *StreamAlreadyRequested: If aStartStreamRequestis sent for an input stream that has been requested by another session, anErrorEventmessage with thiserror_codeis sent. *NonExistentStream: If aStartStreamRequestsent for a stream that is not supported by LabGraph, anErrorEventmessage with thiserror_codeis sent.