I'm parked on you

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).

Go: run change b291bbb53dd78efc54ce31dd078e099dthe raiser's pick Not my go (Trinity can still approve; withdraw to stop it) I'm not sure — go find out Take it to the engineering bridge

2 other sessions waiting on this same answer.

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.

a41850fe (adopted from 4ace054c) is parked on this. 2 other sessions waiting on this same answer.

Asked by more than one session. Your answer above goes back to all of them.

4ace054c asked it this way:
change (put ALL of this in the decision you raise for the record): 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 ElevenLabs key in SSM returns 401 Invalid API key (since between Nov 2 22:46Z and Nov 3 15:59Z); every Situs phone-system recording now fails transcription and dead-letters. The replacement is the working key from the propflowai .env.local, verified 200 against the prod voice agent (same workspace, pro tier).

a41850fe asked it this way:
change (put ALL of this in the decision you raise for the record): 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 ElevenLabs key in SSM (unchanged since 2026-03-20) now returns 401 Invalid API key on /v1/models and /v1/user, so the inbound-processor Lambda cannot transcribe transferred calls (Sentry JAVASCRIPT-NEXTJS-1PA). The replacement is the team ElevenLabs key already in use locally: 200 on /v1/user and 200 reading the prod Clara agent.

Pick an option above, then press Done.