Cannot duplicate components

Support Help
1

Cannot duplicate components using either the left side bar or on the canvas. Refreshing does not do anything.

2

Hello @skhandor Could you please share a short Loom video demonstrating the issue, along with your Agent ID? Please make sure to hide sensitive information before sharing the video.

Thank You

3

Here it is: Retell AI - 14 August 2026 | Loom

Agent ID: agent_8d2d52db59397b38d330af6985

4

Hey @skhandor Checking it with the team.

Thank You

5

Hello @skhandor Thanks for the Loom. Watched it — the click is registering but the UI is silently failing, which points at an error being swallowed on our side rather than something you’re doing wrong. We already have a candidate in the code (the duplicate handler catches errors but doesn’t surface them as a toast), so we’re filing an engineering ticket to fix the silent-failure part regardless.
To pin down why your specific duplicate is failing (version conflict, backend validation, etc.) so we can either unblock you now or give the eng fix the right test case, could you send us two quick things:

  1. Which component were you trying to duplicate — a Subflow inside the current flow (local), or one from your shared components library? (If unsure: local ones live only in this agent’s canvas; shared ones show up in the Components library and can be reused across agents.)
  2. Open DevTools before clicking Duplicate:
    • Console tab — after you click, look for a line starting with Failed to duplicate component: and send us whatever error text follows it.
    • Network tab — filter by conversation-flow. When you click Duplicate, note whether a PATCH /update-conversation-flow (for a local Subflow) or POST /create-conversation-flow-component (for a shared component) request fires, and share the response status + response body.

A screenshot of both tabs after the failing click is perfect. That will tell us the exact backend error the client is currently hiding, and we can usually clear the blocker from there.
As a temporary workaround while we investigate: you can select the nodes inside the component on the canvas, copy, and paste into a new Subflow — this bypasses the failing code path entirely. (Untested for your specific flow, so use only if unblocking urgently.)

Thank You