Troubleshooting ambient documentation
Session start and configuration
The following errors can occur when you start a session or configure its inputs.
| Error | Likely cause | What to do |
|---|---|---|
|
|
An input violated a limit — an unsupported character in |
Validate every input against the character pattern and size limits before you send. Check the section count (1–20) and section headers (alphanumeric only). Use |
|
|
Missing or invalid credentials, or the caller lacks permission. |
Ensure the caller is granted the |
|
|
The domain, subscription, or session referenced doesn’t exist. |
Verify the domain ID, subscription ID, and session ID are correct and active. |
|
|
The request exceeds a service quota. |
Review your service quotas for the service. To request an increase, open the Service Quotas console or create a case in the AWS Support Center. |
|
|
You exceeded the allowed request rate. |
Back off and retry with exponential backoff. |
|
|
A transient service-side error. |
Retry the request. |
Streaming
The following symptoms can occur while a session is streaming audio. InvalidSignatureException is the most common failure — check it first if a stream terminates unexpectedly.
| Symptom | Likely cause | What to do |
|---|---|---|
|
|
Audio is being delivered in large bursts, so signed messages back up in the buffer and their signatures expire (older than 5 minutes) before they’re read. |
Reduce to ~1 second of audio per message and lower the chunk size to ≤ 30,720 bytes. Pace sends at ~500–1000 ms. This is the most common streaming failure — check it first. |
|
A single audio event is rejected |
The chunk exceeded the 32,000-byte maximum. |
Split audio on 30,720-byte boundaries. |
|
The presigned WebSocket URL is rejected |
The presigned URL expired. |
WebSocket presigned URLs allow |
|
Long silences don’t produce output |
Expected — the note is generated from the conversation. |
Ensure audio is actually flowing and that channels are defined correctly. |