### Answer
Based on the available documentation, there isn't a direct way to "re-link" a local component back to an existing shared (library) component after it has been converted to local. [(1) ](
)
Here's what the documentation explains about the conversion behavior:
Convert Between Shared & Local:
- Turn on "Save component to library" to create a shared (library) version.
- Turn off syncing to convert the reference in your agent to a local copy that stops receiving updates.
Publish Behavior (which may relate to your version revert) :
When you publish an agent, the published version snapshots shared components as local copies to prevent future library updates from changing already-published calls.
This means reverting to a previous published version would restore those snapshotted local copies rather than the live shared component links.
Possible workaround:
You would likely need to manually delete the local component nodes from your flow and re-add the shared component from your Library Components tab. This isn't ideal since you'd need to reconnect edges, but the documentation doesn't describe a direct "re-link to existing library component" feature.
I'd recommend reaching out to Retell support for confirmation on whether there's an undocumented way to restore the shared component linkage, as this specific scenario isn't explicitly covered:
- [Contact Sales](
)
- [GitHub](
)