Workflow ends the call with 'Meeting has ended' wi...
# support
v
The "Assistant not valid" status in your logs indicates that your assistant ID is not properly configured. This is likely why your call ends prematurely with the "Meeting has ended" error. Solution: Check that the assistant ID is correctly set on your phone number in the Vapi Dashboard. You need to assign a valid assistant to your phone number to use Voice AI with that number. Sources: - [Discord discussion about Assistant not valid error](https://discord.com/channels/1211482211119796234/1336652401733668864) - [Discord discussion about troubleshooting assistant configuration](https://discord.com/channels/1211482211119796234/1344225187939352586)
s
@Vapi Support Bot I do start the call from the workflow itself, I havent made any numbers or anything, and the call starts and the bot says the first block but after my response just fails
v
When starting calls directly from a workflow, you still need to specify a valid
assistantId
in your API call. Try adding the assistantId parameter to your workflow call:
Copy code
javascript
// Example API call to start a workflow call
const response = await vapi.calls.create({
  workflow: {
    id: "your-workflow-id"
  },
  assistantId: "your-assistant-id", // Add this line
  to: "+1234567890"
});
The "Assistant not valid" error indicates this parameter is missing or incorrect. Sources: - [Discord discussion about Assistant not valid error](https://discord.com/channels/1211482211119796234/1336652401733668864) - [Discord discussion about troubleshooting assistant configuration](https://discord.com/channels/1211482211119796234/1344225187939352586)
c
Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
2 Views