### Answer Based on the available sources, when cloning a conversation flow agent, you need to specify the

conversation_flow_id

in your create-agent API call [(1) ]() . However, the sources don't explicitly document version handling during cloning . The issue you're experiencing suggests that when you clone an agent by referencing only the

conversation_flow_id

, it may not automatically use the latest version (version 35 in your case) . Here's what the cloning process looks like according to the sources : 1. Get the original agent using

/get-agent/{agent_id}

, which returns:

json
{
  "agent_id": "agent_a98aa90805d7655635e47d6136",
  "response_engine": {
    "type": "conversation-flow",
    "conversation_flow_id": "conversation_flow_59effc57691f"
  },
  "voice_id": "11labs-Myra"
}

2. Create a clone using

/create-agent

with the

response_engine.conversation_flow_id

and

response_engine.type

from the response . The sources indicate that conversation flow is still in beta and there are no direct APIs documented for version-specific cloning . To work around this, you might need to: - Use the

/list-conversation-flows

endpoint with

pagination_key_version

parameter to verify which version is being referenced [(2) ]() - Contact support for assistance with version-specific cloning, as this appears to be a limitation of the current beta API I don't have information in the sources about how to explicitly specify a conversation flow version when cloning an agent.

​ To learn more, see the sources I considered: [[1] If i want to clone a conversational flow agent to another workspace how can i do that?](https://discord.com/channels/1186424376300679209/1339179023678574633) [[2] List Conversation Flows](https://docs.retellai.com/api-references/list-conversation-flows) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

Appreciate the feedback! Feel free to ask me again with additional guidance or context.