Dynamic variable issues

[opal basalt]

yeah let's thread it

It sometimes shows that empty state view even when all the dynvar values have been passed correctly 🤷

[signal fable]

what's the point of this lol

but yea i figured it should be used for this

[opal basalt]

most of the dynvar issues are flaky too

maybe they are rolling something out as we speak and that's the reason idk

[signal fable]

yea this makes me uneasy

i'm taking a peek through changelogs to see if anything stands out

https://elevenlabs.io/docs/changelog

[opal basalt]

these issues are ancient

I'm going to grab some convids from today that had some issues and put it all here tomorrow, I suggest you do the same, and then we tag someone from the dev team to take a look

[signal fable]

what issues were they?

[opal basalt]

1. Providing a value for the dynamic_variable and having the conversation get cancelled because "no value provided"
2. Not providing a value for the dynamic variable and the conversation doesn't get cancelled
3. Variable name gets TTS'd instead of the actual value (same as yours)

The last one has been gone for a while but can always come back though. I will fill the list further as soon as I recall all of them lol

[plain cloud]

@wheat shadow @frozen delta do you know if there are issues with this right now? this dynamic variable is not working for us. others are still.

[plain cloud]

it seems like there are new system prompt guardrails on the 11L side that prevent the agent from having this infomration?

[signal fable]

FYI team, i've sent an enterprise email because it's that urgent, in case you guys need to look in the system for it.

[frozen delta]

first time I'm seeing this thread, let me process

is anyone using Twilio? and yes, Conv IDs would be helpful

dynamic variables should appear on the page linked above, correct

[frozen delta]

in general one of team members is working on improving error messaging across the platform so that we can present more helpful debugging info

I believe your problem @signal fable is incorrectly sending the dynamic variables indeed, the message comes as "unrecognized". Can you make sure that the dynamic variables dictionary is correct ?

[signal fable]

I do have this code:

elevenLabsWs.send(
    JSON.stringify({
        type: 'conversation_initiation_client_data',
        dynamic_variables
    })
);

console.log('[II-Open] Sent conversation initiation client data to ElevenLabs.', dynamic_variables);

In which the variable has:

{
  business_id: 'demo_alpha',
  streamSid: '...a1c18c79e...',
  timezone: undefined,
  caller_phone_number: '408...' // This is correct
}

[frozen delta]

can you not send "timezone"?

if undefined ?

maybe that's causing the problem

[signal fable]

can i do ''

empty string

because i had been sending this before, strange that it's not working now

[frozen delta]

you can do empty string (you can also use our system dynamic variable for timezones)

well, let's try to narrow it down

[signal fable]

i can't use that, because it's a business thing

but yea let me try

[frozen delta]

maybe it works, in which case we can add it back, but first let's try to eliminate causes one by one

also, once you do - please send conversation_id here so that I can check quickly

[signal fable]

conv_1901k9w05njxe5mamr1ej50j1q3j

[frozen delta]

cool, let me check

[signal fable]

same deal, but empty string tz

[frozen delta]

can you DM me the code where you're trying to do it ?

I believe you're trying to send it as arbitrary message

whereas conversation_initiation_client_data is the first message that's part of setup

conversation_initiation_client_data must be first message, but certain SDKs might require it as part of start session [not sure]. Are you using any SDK or just direct websocket connection?

[signal fable]

direct WS

i think

yea direct

I'll send you a snippet via DM, but we can keep talking here just so it's helpful for others to search this

I do have to head to sleep since it's very very late here. But i'll catch up afterwards.

[frozen delta]

https://elevenlabs.io/docs/agents-platform/libraries/web-sockets

did you check this guide ?

what I would suggest: moving elevenLabsWs.send() as much up as possible

doing
dynamic_variables: {
...dynamic_variables
}

just to be triple-sure

I 100% see in the logs that we are receiving audio event faster than we receive conversation_initiation_client_data

which is the main culprit because conversation_initiation_client_data must be the first thing we ever receieve

the "what is your phone number" being answered correctly is a red herring as we ourselves add system__phone_number_id (or something like that) as part of system dynamic variables

[signal fable]

i had a really good feeling it was going to be that after i posted it

Okay, i'll try to see how i can prevent it from firing that first

ty @frozen delta !

[signal fable]

ahh yea it's likely a race condition with something i put in

[frozen delta]

perf