Issue with Persistent UUID Display for Deleted Files Causing API and Database Conflicts #109
Description
I’ve encountered an issue on your platform that’s impacting my web application, which integrates with your API. When a file is deleted in the VAPI dashboard (as shown in the attached screenshot), its UUID remains visible in the interface. This behavior is unexpected and causes conflicts with my application’s local database, where the corresponding file UUID is also deleted.
Here’s a clear outline of the problem:
File Deletion: I delete a file from the VAPI dashboard.
Persistent UUID: Despite deletion, the file’s UUID continues to appear in the dashboard (e.g., in the “Add a New File” section, as visible in the screenshot).
API and Database Conflict: My application relies on your API to sync file data. Since the UUID persists in the dashboard, it creates inconsistencies with my local database, where the file and its UUID are removed. This leads to errors in my application’s functionality.
