I have been conducting a systematic evaluation of tl;dv for the past three months, primarily focused on its utility for product analytics and user interview synthesis. A critical part of my workflow involves creating controlled test meetings to validate transcription accuracy, AI summary consistency, and integration behavior with our data warehouse. This has resulted in a substantial library of these test sessions.
I am now encountering a significant operational bottleneck: I cannot delete these old test meetings from my library. The intended process appears straightforward—select meetings and click delete—but the action does not persist. Upon page refresh or navigating away and back, the deleted meetings reappear. I have attempted this from multiple browser environments (Chrome, Safari) and via the desktop application, with identical results.
My troubleshooting steps thus far have been methodical:
* **Cache & Hard Refresh:** Conducted hard refreshes (`Cmd+Shift+R` on Mac) and cleared browser cache entirely.
* **API Consideration:** Reviewed the tl;dv API documentation for a potential direct endpoint. While a `DELETE` method exists for recordings, it requires a specific `recording_id`. The UI does not expose this ID, making manual API calls impractical for bulk cleanup.
* **Pattern Analysis:** Noted that the issue seems to affect older test meetings (from 2+ months ago). More recent test recordings can be deleted without issue. This suggests a possible data migration or indexing problem where older records are in a state that the front-end delete action cannot properly resolve.
This is more than a minor inconvenience. For accurate analysis, my library must reflect only active, relevant meetings. The presence of these obsolete tests:
* Skews my personal meeting count metrics.
* Creates noise when searching for specific client or project meetings.
* Potentially impacts shared workspace views and permissions if test data is inadvertently exposed.
Has anyone else in the community encountered this persistence issue with deleting older recordings? If a resolution has been found, a detailed account of the steps would be invaluable. Furthermore, I am interested in understanding if this is a known platform limitation—perhaps related to meetings recorded before a certain software version—or an undocumented bug.
As a temporary workaround, I am considering tagging all test meetings with a specific keyword (e.g., `#zDELETE_TEST`) to isolate them via search, but this is a suboptimal solution that does not address the root cause of library bloat.
— Amanda
Data > opinions