Getting an error in the dashboard when attempting any edits to the Start Speaking Plan https://cdn.discordapp.com/attachments/1367962358583918713/1367962359037034679/image.png?ex=68167db9&is=68152c39&hm=e6f04f83fa77a26c42d3d17ac659cd3e7911377117987f73dd2a147ad33807a9&

The error occurs because the

transcriptionEndpointingPlan

object is missing or undefined in your Start Speaking Plan configuration. Try adding the required structure to your configuration:

json
"startSpeakingPlan": {
  "waitSeconds": 0.4,
  "smartEndpointingEnabled": false,
  "transcriptionEndpointingPlan": {
    "onPunctuationSeconds": 0.1,
    "onNoPunctuationSeconds": 1.5,
    "onNumberSeconds": 0.5
  }
}

Alternatively, you could try switching your transcriber from Deepgram to Azure, which has resolved this issue for other users. Sources: - [API Reference](https://docs.vapi.ai/api-reference/assistants/get) - [Discord conversation](https://discord.com/channels/1211482211119796234/1334024569861963788)

I'm doing this from the dashboard, it should automatically add that to the structure of the config

According to the documentation I found, Start Speaking Plan configurations can currently only be made via API, not through the dashboard ([docs.vapi.ai/customization/speech-configuration](https://docs.vapi.ai/customization/speech-configuration)). This might explain why you're encountering the error. Have you tried using the API to update your Start Speaking Plan configuration instead? If so, did you encounter any issues with that approach? Source: - [Vapi Documentation](https://docs.vapi.ai/customization/speech-configuration)

That's wrong, I can see it in the dashboard and have used it hundreds of times before with no error.

Hey, really sorry for your experience and for your customers' bad experience as well. If possible, could you record a loom video describing this error/behavior or inconsistency in the dashboard with the steps to reproduce it? That way, I can share this with my team, and we'll take a look. We'll even try to reproduce the same so we can fix it for you. Also, I'll request you to share your assistant ID.

Here you go: https://www.loom.com/share/17643b31abe4483eb175d4626448d13e Assistant id is 0ff49af1-50b1-4993-ab45-9866d43c8990, but it seems to be assistant id agnostic, happens on every assistant i try to edit

@Adam @Shubham Bajaj I also experienced this issue and could only update it via the api. This is likely because your smartEndpointing is set to use livekit. I have the issue for assistants where smartEndpointing is set to livekit. The ones set to use vapi don't have the issue. My asumption is that livekit was removed as an option but there was no fallback to prevent errors for assistants currently using livekit

@Adam thanks for sharing the loom video.

Ah thanks. @Emeka actually we weren't using Livekit

Hey Adam, I checked about this with the team. What has happened is because of your own daily channel, you might have received some beta updates. Can you switch your org channel to weekly and create a new assistant from scratch?