Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. The production ElevenLabs key the inbound processor uses is dead, so office call recordings can't be transcribed and are piling up. Replace it with the working key we already use elsewhere?
The full question, as raised
change: ssm-put-parameter --parameter /propflow/prod/ELEVENLABS_API_KEY --region us-east-1 --type SecureString --value-file: (secret, 51 bytes, never shown) · fingerprint: b291bbb53dd78efc54ce31dd078e099d. Why: the prod SSM ElevenLabs key (v1, set 2026-03-20) returns 401 Invalid API key on /v1/user and /v1/models; the inbound Lambda loads it at cold start, so every office phone recording (pbx_recording) fails Scribe transcription and blocks its FIFO group (alarm propflow-inbound.fifo-oldest-message-age, 2026-11-03 16:00Z). The replacement is the .env.local key, which returns 200 and reads the prod voice agent (same workspace).
Why, and what was tried
The session raising this recommends: Go: run change b291bbb53dd78efc54ce31dd078e099d Prod key 401s on every call; the replacement is verified live and in the same ElevenLabs workspace as the prod voice agent. Tried first, unsuccessfully: Read the Lambda logs (two Scribe 401s at 15:59Z and 16:10Z, ingestPbxRecording), tested the SSM key read-only against ElevenLabs (401) and the .env.local key (200, can read the prod agent). No other path writes SSM.