Blocking Error: Unable to update node in Shared Component

Support Help
1

Hi Support Team,

image
image423×176 4.78 KB

I am writing to report an issue that is preventing me from updating a node in my conversation flow.

The Problem:
I am trying to replace an invalid placeholder number (+1234567890) with a valid number formatted in E.164. However, the system prevents me from saving the changes. It seems to be validating the existing invalid number and blocking the update operation entirely, leaving me unable to correct it.

Error Details:

  • Error Message: “Failed to update node in shared component conversation_flow_component_af94bedca357: The number provided: +1234567890 is not a valid number.”

  • Component ID: conversation_flow_component_af94bedca357

Request:
Could you please look into this or assist me in overriding the current value? I have attached a screenshot of the error for reference.

Best regards,

2

I’m having the same problem - I can’t update ANY node in the flow due to this.

3

Hey @nyescasman I got around this issue. You can update the flow via the API to bypass the UI validation.

Quick fix:

  1. Get your current flow:

       curl -X GET \
     https://api.retellai.com/get-conversation-flow/conversation_flow_component_af94bedca357 \
     -H "Authorization: Bearer YOUR_API_KEY" \
     > current-flow.json

  2. Edit the JSON: find all invalid numbers in transfer_destination.number fields and replace with your valid E.164 number.

  3. Update via API:

      curl -X PATCH \
     https://api.retellai.com/update-conversation-flow/<your_conversation_flow_id> \
     -H "Authorization: Bearer YOUR_API_KEY" \
     -H "Content-Type: application/json" \
     -d @updated-flow.json

The API updates the flow without validating the old values, so you can replace invalid numbers directly.

Note: You’ll need your main conversation_flow_id (not the component ID). Get it from your agent’s response_engine.conversation_flow_id field, or retrieve the full flow structure first.

4

Hello @nyescasman , @trevoruptain do you still have this issue?
If yes, please provide the agent IDs, and I will get it fixed for you, so you don’t have to do it through the API every time.

Thank you.