Anynone knows how to fix this error from UI? I tried but is impossible beacuse i cant even change a simple letter. Also i cant connect edges to new connections… I have 2 components with this issue and i dont know why. Maybe empty edges that i dont know why are empty, because i connected before publish.
I need help to fix that. Thanks.
Thank you for reaching out to Retell AI Support. We’ve received your ticket and our team will respond within 8 hours.

Hi Retell,
Thank you for reaching out. To help us investigate your agent and any potential suspension, could you please provide the following:
- If a particular agent was banned, what is the agent ID?
- What was the purpose of this agent?
- Proof of your company’s registration document.
- Your company’s website (if available).
- If you are speaking on behalf of another company, an authorization letter.
If you’re unable to provide any of these details, just let us know and we can proceed accordingly.
Best,
Evy AI
AI Support Agent @ Retell AI

It seems there is a general service degradation happening at the moment - we are seeing the same HTTP 400 error when trying to update nodes.
@support2 this is an urgent issue with production impact
Also getting this 400 error when trying to update any agent.
I am also getting 400 bad request errors when trying to create a transition! Same error when trying to import an agent through a json file. please fix the issue
Same here, getting 400 for all our agents when trying to change something.
Figured out what’s causing this. Retell pushed a schema change that broke agents containing extract_dynamic_variables nodes with variables set to type string. Their API now only accepts enum as a valid variable type for those nodes, and any agent with an old string-type variable fails validation on every update request — even unrelated ones — which is why you can’t change anything at all in the UI.
The fix:
-
Export your agent as JSON and search for any extract_dynamic_variables nodes — look for variables with "type": "string". That tells you which nodes are broken and what variable names to look for.
-
Back in the UI, find those nodes in your conversation flow, open the variable settings, and change the type from String → Enum and make sure at least one choice is defined.
-
Save — your 400 errors should clear immediately and you’ll be able to edit normally again.
No need to manually edit or re-import JSON. Just use the export to identify which nodes and variables are affected, then fix them directly in the UI.
@duncan
Can you share the Agent ID?
Hey @Omar_Ashraf, my particular agent id is agent_2fbfc5839bf1ebecfcb3f76d02
Thanks @alacer.ben
The team is checking right now
Hi,
agent_1e44f89904f7c53f64ede6495a
agent_62334ab3b52364677283a790bb
This should be fixed now.
1 Like
Hi, I could fix one component but the error in the other one still going. The component ID is conversation_flow_component_698f529f0bf9. The agent ID is: agent_6efa8f210f668a4dcff4101068
Yeah, now is workinf perfect. Thank you so much!