document start_recognition_timeout error

Author: JamesG-Speechmatics

docs/api-ref/realtime-transcription-websocket.mdx

@@ -171,6 +171,7 @@ In the Realtime SaaS, an in-band error message can be followed by a WebSocket cl
 | 4005 | `quota_exceeded` |
 | 4006 | `timelimit_exceeded` |
 | 4013 | `job_error` |
+<!-- | 4xxx | `start_recognition_timeout` | TODO -->
 
 {/* Manually generated TOC, since we're using JSX sections */}
 export const toc = [

spec/flow-api.yaml

@@ -234,6 +234,7 @@ components:
         - job_error
         - internal_error
         - unknown_error
+        - start_recognition_timeout
 
     ToolTypeEnum:
       type: string

spec/realtime.yaml

@@ -1267,6 +1267,7 @@ components:
         | `not_allowed` | User is not allowed to use this message (is not allowed to perform the action the message would invoke). |
         | `job_error` | Unable to do any work on this job, the server might have timed out etc. |
         | `protocol_error` | Message received was syntactically correct, but could not be accepted due to protocol limitations. This is usually caused by messages sent in the wrong order. |
+        | `start_recognition_timeout` | The timeout for sending StartRecognition has been exceeded (SaaS only) |
         | `quota_exceeded` | Maximum number of concurrent connections allowed for the contract has been reached |
         | `timelimit_exceeded` | Usage quota for the contract has been reached |
         | `idle_timeout` | Idle duration limit was reached (no audio data sent within the last hour), a closing handshake with code 1008 follows this in-band error. |
@@ -1289,6 +1290,7 @@ components:
         - not_allowed
         - job_error
         - protocol_error
+        - start_recognition_timeout
         - quota_exceeded
         - timelimit_exceeded
         - idle_timeout