Error: Agent step's exit condition names are in Arabic (not supported string)
Is it not possible to set up the exit conditions in Arabic?
I tried to write the name and the LLM description in Arabic, but the step didn't work. It suddenly ends the chat whenever I try to test it out.
But when I rewrite them in English, it worked even though the prompt itself is still in Arabic
Is there any setting I should switch to Arabic??
4 Replies
You don’t need to “switch” Voiceflow into Arabic and there’s no hard-coded language restriction on Exit Conditions—the LLM will read whatever language you put in the Name and LLM Description fields.
When the conversation dies right away it’s almost always one of these reasons ⬇️ 1️⃣ No path is connected to the Exit Condition
• If the agent matches your Arabic exit condition but that node isn’t wired to the rest of the flow, the session ends.
• Double-check that every exit condition (and the Default path) is connected to another step. 2️⃣ The LLM can’t confidently match the user’s Arabic utterance
• In the Instructions (top of the Agent step) explicitly tell the model to respond and reason in Arabic, e.g.
“تحدث بالعربية فقط وأطابق نوايا المستخدم المكتوبة بالعربية.”
• Inside the Exit Condition’s LLM Description, keep the explanation in Arabic and add a few example phrases the user might say.
مثال:
“فعّل هذا الخروج عندما يقول المستخدم «أريد إرجاع المنتج» أو «كيف أطلب استرجاعًا؟»…” 3️⃣ Required variables aren’t satisfied
• If you added a required entity/variable, make sure the agent can collect it (entity definition in Arabic or custom entity + rules).
• Otherwise the agent will drop to Default (or end) instead of the exit path. 4️⃣ Default entity language limits (only if you rely on built-in entities)
• Built-in entity types are language-specific. For Arabic projects create Custom Entities or write natural-language Rules. Quick checklist
✓ Agent Instructions specify Arabic.
✓ Exit Condition: Arabic name + Arabic LLM description + examples.
✓ All exit paths—including Default—are connected to a step.
✓ Any required variables/entities are available in Arabic (or Custom).
✓ Test again in the Simulator with Arabic utterances. If everything is connected and the Instructions/Descriptions are in Arabic, the exit condition will fire just like the English one. هناك لا حاجة لأي إعداد إضافي.
When the conversation dies right away it’s almost always one of these reasons ⬇️ 1️⃣ No path is connected to the Exit Condition
• If the agent matches your Arabic exit condition but that node isn’t wired to the rest of the flow, the session ends.
• Double-check that every exit condition (and the Default path) is connected to another step. 2️⃣ The LLM can’t confidently match the user’s Arabic utterance
• In the Instructions (top of the Agent step) explicitly tell the model to respond and reason in Arabic, e.g.
“تحدث بالعربية فقط وأطابق نوايا المستخدم المكتوبة بالعربية.”
• Inside the Exit Condition’s LLM Description, keep the explanation in Arabic and add a few example phrases the user might say.
مثال:
“فعّل هذا الخروج عندما يقول المستخدم «أريد إرجاع المنتج» أو «كيف أطلب استرجاعًا؟»…” 3️⃣ Required variables aren’t satisfied
• If you added a required entity/variable, make sure the agent can collect it (entity definition in Arabic or custom entity + rules).
• Otherwise the agent will drop to Default (or end) instead of the exit path. 4️⃣ Default entity language limits (only if you rely on built-in entities)
• Built-in entity types are language-specific. For Arabic projects create Custom Entities or write natural-language Rules. Quick checklist
✓ Agent Instructions specify Arabic.
✓ Exit Condition: Arabic name + Arabic LLM description + examples.
✓ All exit paths—including Default—are connected to a step.
✓ Any required variables/entities are available in Arabic (or Custom).
✓ Test again in the Simulator with Arabic utterances. If everything is connected and the Instructions/Descriptions are in Arabic, the exit condition will fire just like the English one. هناك لا حاجة لأي إعداد إضافي.
I have checked all the mentioned, and it still didn't work with Arabic exit conditions. Only English
Fun fact: the whole workflow was built with Voiceflow's own prompter
Every agent of these doesn't work as shown in the screenshots.
Is there a way to solve this issue other than going through all of them and translating the exit conditions, both the name and the LLM description, into English?
Here: working with English exit conditions
this is the execution failure debug logs and apparently the tool name (aka exit condition) must contain: letters (a–z, A–Z), numbers (0–9), underscores (_), or hyphens (-) therefore Arabic letters are not supported
attached the execution error log and the debug log showing all the tools names
once I change the exit condition name into English and keep the LLM description in arabic, the agent works
kindly asking voiceflow development team to fix this Arabic string issue ASAP