Update streaming error code numbers in session errors table#660
Merged
Update streaming error code numbers in session errors table#660
Conversation
- Add new codes 3006 (User Input Validation Error), 3007 (Input Duration Error), 3008 (Session Expired Error), 3009 (Concurrency Exceeded Error) - Remove rows from 3005 that are now covered by new specific codes - Remove 1008 concurrent sessions row (now covered by 3009) - Keep 3005 as catch-all for generic server errors - Add note about 3005 catch-all behavior - Update Handling closed sessions example to reference new 3008 code Co-Authored-By: unknown <>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Co-Authored-By: unknown <>
Per engineer feedback: keep all original reason strings and descriptions exactly as they were. Only update the code numbers: - 3005 -> 3008 for Session Expired row - 3005 -> 3007 for Input duration violation row - 3005 -> 3006 for Invalid Message Type, Invalid JSON, Invalid Message rows - 3005 -> 3007 for Audio Transmission Rate Exceeded row - 1008 -> 3009 for Too many concurrent sessions row - Keep 3005 Session Cancelled, 1008 Missing Authorization, 1008 <reason> unchanged Co-Authored-By: unknown <>
devin-ai-integration
bot
changed the title
aurpsis-aai
approved these changes
Feb 24, 2026
Contributor
|
@dylan-duan-aai review plz convo here |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the error codes table on the Common session errors and closures page. Previously, most error rows used the generic
3005code. This PR reassigns them to new, more specific codes while preserving every original row, reason string, and description exactly as-is.Code number changes (reason strings and descriptions unchanged):
3005→3008: "Session Expired: Maximum session duration exceeded"3005→3007: "Input duration violation:<time>ms. Expected between 50 and 1000 ms"3005→3006: "Invalid Message Type:<message>"3005→3006: "Invalid JSON:<json>"3005→3006: "Invalid Message:<message>"3005→3007: "Audio Transmission Rate Exceeded: Received<time>sec. audio in<time>sec"1008→3009: "Unauthorized Connection: Too many concurrent sessions"Rows kept unchanged (no code change):
3005— "Session Cancelled: An error occurred"1008— "Unauthorized Connection: Missing Authorization header"1008— "Unauthorized Connection:<reason>"Other changes:
<Note>explaining that3005is still used as a catch-all for server-side errors3008instead of3005Updates since last revision
Per engineer feedback, reverted the earlier approach that consolidated rows into new reason strings. Now all original rows are preserved verbatim — only the code numbers are changed.
Review & Testing Checklist for Human
3006/3007/3008/3009are the correct codes for each error scenario<Note>render correctly3005catch-all note wording — it says "not covered by the more specific codes above" — verify this reads clearly given3005appears mid-tableNotes