Error when publishing assistant
# support
t
Hello, I am experiencing an issue when selecting the “French conversational lady” voice from Cartesia in the assistant’s Voice Configuration. Important note: when I click “Talk to Assistant”, the voice works correctly and audio is generated as expected. However, when I click "Publish", the error occurs. This issue happens only with this specific voice. All other Cartesia voices work correctly both in test mode and after publishing. When I click on the "Publish" button, I receive the following error message (see attached screenshot): Couldn't find Cartesia Voice: a249aeff-1e96-4d2c-b23b-12efa4f66f41. Tip: If this is a custom voice, ensure you're using your Cartesia credentials. This is not a custom voice, so I believe this is a bug related to the publishing process or voice resolution for this specific Cartesia voice. Thank you in advance for your assistance. https://cdn.discordapp.com/attachments/1462109989253415005/1462109990495064064/image.png?ex=698b520a&is=698a008a&hm=9b344d54d18594ce9aa3de77d61a37c59152de983abb416d475b58bee274621d& https://cdn.discordapp.com/attachments/1462109989253415005/1462109991149506610/image.png?ex=698b520a&is=698a008a&hm=5a085326a796c2f279fe8dc51d47b3e052cd553b9bc20bee9a4e7a4f2b0ab077&
c
Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team
v
Action Required: Please report this publishing issue to the Vapi team using their recommended format for dashboard/UI bugs. Include your screenshots, browser version, steps to reproduce, and the exact error message. You can follow this example:
Copy code
Issue: Error when publishing assistant with Cartesia "French conversational lady" voice  
Steps: 1. Select voice in configuration 2. Click "Publish"  
Expected: Voice publishes successfully  
Actual: Error "Couldn't find Cartesia Voice: a249aeff-1e96-4d2c-b23b-12efa4f66f41"  
Browser: [Your browser/version]  
Screenshots: [Attach images]
This will help the support team resolve your issue quickly. (See the [issue reporting guide](https://docs.vapi.ai/issue-reporting) for more details.) Source: - [Issue Reporting](https://docs.vapi.ai/issue-reporting)
j
Thanks for sharing this, since the voice works in test but breaks on publish, this almost always points to a voice ID sync or permission issue between Vapi and Cartesia, not something you did wrong. It’s likely that specific voice ID isn’t resolving correctly at publish time. Re-syncing voices or manually pasting the ID usually fixes it. I can help you confirm what’s happening on your side. Are you using a personal Cartesia API key or a shared/team one? @tancfire
t
Hello, I didn't use any Cartesia API key. I already tried to copy/paste the voice ID manually in the voice configuration, but the field go back automatically to the list (it probably detects the ID voice as one of the list). I don't know what you mean by re-syncing the voices. Can you provide me the steps to do that ?
j
Since you’re not using an API key, the issue is likely with how Vapi is resolving that specific Cartesia voice in the publishing workflow. When I mention “re-syncing,” I mean refreshing your Vapi dashboard so it fully pulls the latest list of voices from Cartesia — this often fixes cases where a voice is in the dropdown but can’t be published. I can walk you through the exact steps privately and help make sure this voice works properly when you publish. Would you like me to guide you through it step by step? @tancfire
t
Oh, ok. I already refreshed my browser (CTRL+F5), close/re-open the browser and the error was still here.m, unfortunetly.
c
Hi, It seems that the voice (a249aeff-1e96-4d2c-b23b-12efa4f66f41) was removed from Cartesia (https://play.cartesia.ai/voices?q=a249aeff-1e96-4d2c-b23b-12efa4f66f41). Please use another voice instead.