Hello everyone,
I’ve been conducting a detailed evaluation of Otter.ai’s capabilities for a client’s enterprise knowledge management workflow, and we’ve hit a significant technical snag during our integration testing phase. Specifically, we are encountering consistent failures when attempting to import audio and video files from a linked Dropbox Business account, but only for files larger than approximately 200MB. Smaller files in the same folder and format import without issue.
This is a critical path item for us, as the intended workflow relies on processing lengthy recorded meetings and seminars. The failure manifests as an indefinite “Processing” state in the Otter.ai interface, followed by a generic error message after a long wait, or sometimes the import simply never initiates. We’ve replicated this across multiple file types (.mp4, .m4a, .mov) and from different Dropbox team member accounts.
As part of my standard procurement playbook, I’ve already stepped through the basic troubleshooting checklist:
* Verified the Otter.ai and Dropbox integration is properly authorized and has the necessary permissions.
* Confirmed network stability and that corporate firewalls are not blocking the transaction.
* Ensured the file formats are within Otter’s stated specifications.
* Attempted the import via both the web portal and the desktop application with identical results.
The pattern strongly suggests an undocumented platform limitation or a timeout/threshold in the server-side import pipeline. Before I escalate this through official vendor support channels, I wanted to tap the community’s practical experience.
My key questions for those who may have navigated this:
* Has anyone successfully imported a file from Dropbox (or similar cloud storage) that significantly exceeds 200MB? If so, were there any specific steps or workarounds required?
* Is this a known, documented constraint that I’ve simply missed in the service specifications?
* In your evaluation or daily use, what has been your effective maximum reliable import size from cloud storage, and did you find it differed from direct uploads?
Understanding this limitation is essential for my vendor scoring matrix, particularly under the “Technical Integration & Scalability” criterion. Any insights into this behavior, or confirmed workarounds like chunking files pre-upload, would be immensely valuable for our procurement decision and implementation planning.
null
You've hit on the classic bait and switch with these integrated cloud services. The "unlimited" import promise in the sales demo meets the real-world API transfer limits and timeouts buried in the technical annex.
You need to check your contract's service level appendix, not the troubleshooting guide. There's likely a clause about maximum object size for third-party integrations. They'll call it a Dropbox limitation, Dropbox will point back to Otter's API implementation. Meanwhile, your workflow is stuck.
This is why we never approve a purchase without a full-scale, worst-case load test using the client's actual data. The sales team never brings up the 200MB soft ceiling.
Show me the data