Assistant no longer functional when connected to Blob Storage
Hello all,
I have been trying to make the switch from Vapi's call storage to storing calls in my own Blob Storage Container, however, I've run in to some issues.
I updated one of my assistants via API call with my Blob Storage credentials in the format of:
curl -X PATCH https://api.vapi.ai/assistant/{assistantID} \
-H "Authorization: Bearer {APIKey}" \
-H "Content-Type: application/json" \
-d '{
"credentials": [
{
"provider": "azure",
"service": "blob_storage",
"bucketPlan": {
"connectionString": "{connectionString}",
"containerName": "{containterName}",
"path": "{pathName}"
}
}
]
}'
After running that cURL (with the correct info in place of the placeholders), my assistant stopped working, they wouldn't speak their first message, they wouldn't respond to any user prompting, nor make any tool-calls.
I then configured Blob Storage at an Organization level using the dashboard. I used a different assistant to test and found that they would speak their first message, however, they would stop working after their first tool-call and would stop responding to user prompting.
I did also notice that, although assistants were no longer working properly, .wav entries were being made in my Blob Container, so names and permissions are not the issue.
Also, the first tool-call does succeed, but when blob storage is enabled, the assistant stops responding post-call, as if it "freezes" and does not respond to any user prompting and the call will timeout due to silence.
I've attached two screenshots showing expected output and actual.
I’ve tested this across multiple assistants I’ve built, including rolling back changes. The issue consistently appears only when blob storage is enabled.
Is this potentially a bug on Vapi's end?
Thanks!
I have been trying to make the switch from Vapi's call storage to storing calls in my own Blob Storage Container, however, I've run in to some issues.
I updated one of my assistants via API call with my Blob Storage credentials in the format of:
curl -X PATCH https://api.vapi.ai/assistant/{assistantID} \
-H "Authorization: Bearer {APIKey}" \
-H "Content-Type: application/json" \
-d '{
"credentials": [
{
"provider": "azure",
"service": "blob_storage",
"bucketPlan": {
"connectionString": "{connectionString}",
"containerName": "{containterName}",
"path": "{pathName}"
}
}
]
}'
After running that cURL (with the correct info in place of the placeholders), my assistant stopped working, they wouldn't speak their first message, they wouldn't respond to any user prompting, nor make any tool-calls.
I then configured Blob Storage at an Organization level using the dashboard. I used a different assistant to test and found that they would speak their first message, however, they would stop working after their first tool-call and would stop responding to user prompting.
I did also notice that, although assistants were no longer working properly, .wav entries were being made in my Blob Container, so names and permissions are not the issue.
Also, the first tool-call does succeed, but when blob storage is enabled, the assistant stops responding post-call, as if it "freezes" and does not respond to any user prompting and the call will timeout due to silence.
I've attached two screenshots showing expected output and actual.
I’ve tested this across multiple assistants I’ve built, including rolling back changes. The issue consistently appears only when blob storage is enabled.
Is this potentially a bug on Vapi's end?
Thanks!
