Cannot Load Assistants in Dashboard
# support
r
Getting this error message. Tried on two different browsers, reloaded, etc. Something Went Wrong! undefined is not an object (evaluating 't.smartEndpointingPlan')
a
Hey, Could you please schedule a brief call at your convenience so we can discuss this matter in detail? Kindly use the following link to book a suitable time: .
r
Thanks. However per your calendly you have no times available till June 24th. VAPI Dashboard is unusable to me now, and I need access to support our business development, which will be mutually beneficial, I believe (likely to lead to enterprise relationship). But even if that weren't the case, the product is seriously hobbled. I seem to still have API access, but do need Dashboard access to Assistants as well. Can you not help help me get access back via DM?
Still cannot access Assistants. A VAPI team member kindly offered to schedule a call, but his schedule has no openings till June 24th, well after I'd have to find an alternative to VAPI if I continue to not be able to access Assistants in the Dashboard. cc: @Shubham Bajaj @VAPI Tech
I puzzled it out. Apparently there has been a change to the Assistant data structure, and a "smartEndpointingPlan" parameter needs to created and set in my assistants. If there was a notification of this, I missed it. Since the Dashboard doesn't allow me to load any assistants, will have to do this via API.
a
API is definitely the most customizable experience and if you would like any assistance with setup or troubleshooting regarding this, please let us know.
Also can you send a loom screen recording for the dashboard issue where your assistants aren't loading?
r
I don't use loom but I'll get you a screenshot here. I have set up an api call that adds the smartEndpointingPlan to my assistants (also created via API call) and they will now load in the Dashboard.
v
To resolve the Dashboard loading error, update your assistants via the API to include the new
smartEndpointingPlan
property.
Here's a sample payload for the update:
Copy code
json
{
  "startSpeakingPlan": {
    "smartEndpointingPlan": { "provider": "vapi" }
  }
}
This change should allow your assistants to load in the Dashboard again. [See changelog for details](https://docs.vapi.ai/changelog/2025/5/3) Sources: - [Vapi Changelog May 3, 2025](https://docs.vapi.ai/changelog/2025/5/3) - [Vapi API Reference: Update Assistant](https://docs.vapi.ai/api-reference/assistants/update)
r
Thanks Bot. This is how I figured it out, by looking at the ChangeLog. The error message could be more informative though. Would have saved me a day and a half of scratching around to find out what's wrong.
v
It looks like your assistants are now loading, but you're seeing a new error about
transcriptionEndpointingPlan
.
Could you please confirm if you have added a valid
transcriptionEndpointingPlan
object to each assistant's
startSpeakingPlan
(similar to how you added
smartEndpointingPlan
)? This parameter appears to be required based on the latest API documentation and your error message. If you need an example structure, let me know! Sources: - [VAPI API Reference: Update Assistant](https://docs.vapi.ai/api-reference/assistants/update?explorer=true) - [VAPI API Reference: Create Assistant](https://docs.vapi.ai/api-reference/assistants/create?explorer=true)
To resolve the dashboard loading error, ensure each assistant's
startSpeakingPlan
includes both
smartEndpointingPlan
and
transcriptionEndpointingPlan
.
Here’s a sample structure you can use in your API call:
Copy code
json
"startSpeakingPlan": {
  "waitSeconds": 0.4,
  "smartEndpointingPlan": { "provider": "vapi" },
  "transcriptionEndpointingPlan": {
    "onPunctuationSeconds": 0.1,
    "onNoPunctuationSeconds": 1.5,
    "onNumberSeconds": 0.5
  }
}
Update your assistants with this structure via the API, then reload the dashboard. This should resolve the "Cannot read properties of null (reading 'transcriptionEndpointingPlan')" error. [See more in the speech configuration docs.](https://docs.vapi.ai/customization/speech-configuration) Sources: - [Speech configuration documentation](https://docs.vapi.ai/customization/speech-configuration) - [Vapi Changelog May 3, 2025](https://docs.vapi.ai/changelog/2025/5/3)
a
Glad the issue was resolved. Please reach out to us if you have any other questions regarding this issue
r
Thank you! Would suggest more informative messages, particularly for breaking changes. Appreciate the help.
v
Thank you so much for your feedback! Clearer and more informative error messages are really important, especially when there are breaking changes. Your suggestion is appreciated and will help improve the experience for everyone. If you have any more thoughts or ideas, feel free to share!
Thank you so much for your feedback and for sharing your experience. Your suggestion about making error messages more informative—especially around breaking changes—is really valuable and will help improve the experience for everyone. We're glad you were able to resolve the issue!
2 Views